On Thu, 19 Feb 2015 09:37:49 +1100, Chris Angelico <ros...@gmail.com> wrote:
>On Thu, Feb 19, 2015 at 9:17 AM, <ru...@yahoo.com.dmarc.invalid> wrote: >>> SQLite3 is fine for something that's basically just a more structured >>> version of a flat file. You assume that nobody but you has the file >>> open, and you manipulate it just the same as if it were a big fat blob >>> of JSON, but thanks to SQLite, you don't have to rewrite the whole >>> file every time you make a small change. That's fine. >> >> That's bullshit. Sqlite offers a lot more than that including >> a SQL interface, transactions, referential integrity, constraints >> indexes, triggers and other general relational database features. >> >> That you would equate that to a JSON blob would indicate either >> a profound ignorance about Sqlite or (more likely) a need to >> defend your preference with complete disregard of fact. > >I didn't equate them. I said that SQLite3 is great if you look on it >as an upgrade over a JSON blob. Of course it offers more features than >that, and you don't need to swear at me to make your point. > >But SQLite3 is *not* great if you look on it as a database engine >comparable with DB2, PostgreSQL, and even MySQL. And how does that answer the OP's question? -- Steve Hayes from Tshwane, South Africa Web: http://www.khanya.org.za/stevesig.htm Blog: http://khanya.wordpress.com E-mail - see web page, or parse: shayes at dunelm full stop org full stop uk -- https://mail.python.org/mailman/listinfo/python-list
