Re: Using SQLite in production

On Thu, Jul 3, 2008 at 8:28 PM, Alex Slesarev <[EMAIL PROTECTED]> wrote: > One more issue - if you change a model, then you have to drop database > and recreate it using syncdb (sqlite do not allow modifying tables and > columns). It is not so good for production use. This is not quite correct.

Re: Using SQLite in production

One more issue - if you change a model, then you have to drop database and recreate it using syncdb (sqlite do not allow modifying tables and columns). It is not so good for production use. -- Best regards, Alex Slesarev. --~--~-~--~~~---~--~~ You received this

Re: Using SQLite in production

On Jul 2, 10:20 pm, David Marko <[EMAIL PROTECTED]> wrote: > I'm just considering using SQLite in small Django project(in > production environment). I have no fear about performance but what > troubles me is whether SQLite can be used in environment like Apache > +mod_wsgi? As SQLite is file

Re: Using SQLite in production

I don't have any firsthand experience to share with running sqlite in a production setting. I did choose to spend about 30 seconds scanning the sqlite FAQ: http://www.sqlite.org/faq.html#q5 http://www.sqlite.org/faq.html#q6 If what sqlite is saying on their FAQ is true, it sounds you can get

Using SQLite in production

I'm just considering using SQLite in small Django project(in production environment). I have no fear about performance but what troubles me is whether SQLite can be used in environment like Apache +mod_wsgi ? As SQLite is file based database, isn't there concurrency problem? Can someone explain?