-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 25/01/12 20:29, Ryan Macy wrote: > I was trying to say that I don't believe this would have anything to > do with SQLite, you would have to deal with these issues regardless of > the solution that is selected.
Those issues (identity, authentication, authorization) are already addressed in MySQL, Postgres, Oracle and many other databases. You'd have to invent a new solution if using SQLite and it will be a lot of work that they have already done for you. > That is a good point, I will need to take that into consideration. > Multiple queries, and queries that all rely on each other, are items I > have been struggling to conceptualize implementation for. It presents > an interesting problem. If you love JSON and Python (count me in on both counts) then I strongly recommend you take a look at MongoDB (and pymongo). (MongoDB has many good language bindings and isn't Python specific.) The query language is essentially JSON. You store your data denormalized so you have fewer issues with data items relying on other items. Note that MongoDB isn't engineered to be exposed to the raw Internet either, although it does have authentication and (weak) authorization. In general you wouldn't really want to expose any kind of database service directly to arbitrary clients supplying SQL. Instead you put up a front end - REST semantics and JSON are recommended, with your front end code then accessing the database behind the scenes. A year ago I was doing lots of work to take Postgres database dumps, feed them into SQLite and then denormalize the data into MongoDB ... Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk8g2SUACgkQmOOfHg372QQMNgCeO7e0hGuEAadXpBFSOKHFmmDn odAAoKCyRU3Ms5f9/SBxw2amSLrKGZyw =8OTf -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
