SQLite is great as long as it's used for what it's good at. Should be perfect for organizing data in any single user application, including things like Android apps, desktop apps, or single player locally installed games.
It can also be handy for development since it can be used locally and you don't have to worry about managing a dbms. Django does this as the default, but it's intended for local development only. You'd then use something else for release. Any sort of multi-user application and you'll want to use something like postgresql or mysql. Locking the whole db for each action just isn't practical with multiple simultaneousness users. On Sun, Sep 12, 2010 at 2:05 PM, Bill Barry <[email protected]> wrote: > On Sun, Sep 12, 2010 at 1:01 PM, Fred James <[email protected]> > wrote: > > This query may be only partially off topic ... I am shall be limiting > > the OS choice to Linux > > I am seeking comment ... why would I not want to use SQLite? Of course, > > comments as to why I might wish to use SQLite are welcome as well. > > I do have some experience with Oracle and MySQL, and other types of > > databases in general. > > Thank you > > Regards > > Fred James > > > > Sqlite stores the database in single file and locks that file on write > so that you can't do simultaneous reads and writes. This would slow > down a system in extremely heavy use conditions. I.e. many > reads/writes per second. > If you will not be in this situation it's a very nice database. > > Bill Barry > _______________________________________________ > EUGLUG mailing list > [email protected] > http://www.euglug.org/mailman/listinfo/euglug >
_______________________________________________ EUGLUG mailing list [email protected] http://www.euglug.org/mailman/listinfo/euglug
