Javascript Object -> SQL, in Javascript

Question

I have a simple client-side Sqlite database (via. Google Gears) I want to use for persistence of the contents of a javascript object's properties (not methods). I don't really care about normalization since it has lots of potentially disparate fields (primitive types, arrays, objects) that would thwart normalization anyway.

What would be the best way to go about doing this? Or in the worst case, an alternative that at least achieves persistence?

Sean Vieira · Accepted Answer · 2010-09-17 20:47:47Z

1

If you don't need type information for your objects (and they contain no methods, only attributes) why not store your data as JSON?

answered Sep 17, 2010 at 20:47

Sean Vieira

161k34 gold badges321 silver badges297 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

Hamster Over a year ago

And do what with that JSON data that persists it? Stick it all in one big string in a single-item database table?

Sean Vieira Over a year ago

If you're only using it for persistence and you're not versioning the object in question, then yes, just a single column table will do.

Sean Vieira Over a year ago

@Hamster -- Glad I could help! The reason I suggest this approach is for speed. Breaking down the object (which will have many disparate fields) just for persistence will slow down the speed of serializing / deserializing the object -- and, according the OP, add no needed functionality to what is being built. Simplicity wins over nifty. :-)

Collectives™ on Stack Overflow

Javascript Object -> SQL, in Javascript

1 Answer 1

3 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

3 Comments

Your Answer

Sign up or log in

Post as a guest

Related