On Fri, Apr 15, 2016 at 3:04 PM, R Smith <rsmith at rsweb.co.za> wrote:
> > That's great news :) > Let me just note that we do not really shun the likes of Postgress, MSSQL, > MySQL etc. - those systems answer a different need. If you for instance > want to store secret information with per-table user access controls, or > run a networked client-server kind of data model, then you should not use > SQLite, you should really use one of those. SQLite is much better for local > storage though, and even as a software data storage for your own software - > as Richard delightfully likes to point out (I'm paraphrasing a bit since I > cannot recall the actual quote) - "We'd like you to not think of SQLite as > a replacement for Postgress/MySQL/etc.... We'd like you to think of it as > a replacement for fOpen()." > I am not really a developer. More of a dilettante programmer. ?But this last is how I think of ?using SQLite. I use for permanent storage, in preference to reading regular file and putting the data into something like a Java Hashmap. > > > Cheers, > Ryan > -- "He must have a Teflon brain -- nothing sticks to it" Phyllis Diller Maranatha! <>< John McKown
