It is true that it is not a client-server database. But it is far more powerful than the name hints. Also, it seems that some of Massimo's information is incomplete. I'll try to flesh it out a little more.
1) True. However, it is magnitudes times faster than MySQL and PostgreSQL which allows it to handle a similar number of accesses sequentially. 2) Not true. The number of records is not what limits SQLite, rather it is the logical size of the database file. The SQLite docs suggest that "If you need to store and modify more than a few dozen GB of data, you should consider using a different database engine." see: http://sqlite.org/whentouse.html 3) The only reference I can see to anything related to this was fixed in 2005. see: http://www.sqlite.org/cvstrac/wiki?p=DatabaseCorruption 4) True for Python, but false in general, see: http://sqlite.org/backup.html I get 10000-15000 unique hits per day and I use SQLite for most of my new stuff. The only time I ran into concurrency issues was when I was experimenting with SQLite as a session backend. I swapped back over to using files and things have been fine since then. -tim mdipierro wrote: > sqlite is not a client server database this means: > > 1) the entire database is locked when a connection is open, has no > concurrency whatsoever > 2) it will become slow with large number of records > 3) it gets corrupted if you run out of disk space > 4) does not provide a way to backup the database when its being > accessed. > > Bottom line: sqlite is fine if you have few data and few users. > > The book has instructions on how to run postgresql. You must run from > source and install the psycopg2 driver. > > Massimo > > > On Mar 25, 8:34 am, ural <cevdetu...@gmail.com> wrote: > >> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - >> mdipierro To: web2py >> 09 March 2009 >> [web2py:17722] Sqlite disaster >> >> For a production site I suggest using postgresql. >> >> I have seen very bad failures of sqlite when for example you run out >> of disk space. Complete database corruption. >> >> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - >> >> Hi, >> >> I was realy surprised when i read the massage above in "User's group". >> I thought 'sqlite' is the best db for every application made in >> web2py. >> Now, i am curious what kind of problems can i meet while using >> sqlite. >> >> It can prevent some ocassions to know about "experienced problems with >> sqlite". >> A Tutorial about the usage of different databases in web2py could be >> very usefull. >> >> I have now PostgreSQL in my machine(windows xp) installed. >> But to built relation postgresql with python seems to be a frustrating >> work for me. >> >> İs there any recipe you can recommend for guiding postgresql- >> installation with python ? >> >> thanks >> >> ural >> > > > -- Timothy Farrell <tfarr...@swgen.com> Computer Guy Statewide General Insurance Agency (www.swgen.com) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
