-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/07/13 16:19, Simon Slavin wrote: > <http://unqlite.org>
What has generally become important to me is being able to supply arbitrary JSON as a "record", be able to query it, and get the same arbitrary JSON back out. In addition to unqlite, some of the other "nosql" databases have the same approach (eg MongoDB). Even postgres is adding JSON storage via hstore. What hasn't standardised is how you query which means you can't easily change engines or write (mostly) portable code like you can with SQL. MongoDB uses JSON shaped structures with $prefixed operators. unqlite is using a custom Jx9 interpreted language. And postgres uses minor extensions to SQL. There was unql which DRH was involved in two years ago, but appears unadopted. My favourite is the MongoDB approach since the queries and data are substantially similar - it is very similar to Query By Example. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlHaGJwACgkQmOOfHg372QTXaQCgkiy49SE5bHyvRr8gn+Oecgve kSMAoLcq1ZXRg4Z5KXdU3HsfT9CkyqhE =J/3c -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
