Thanks, it's an in-house thing so I don't anticipate growth.
I guess i'll stick with sqlite for now.
Your reassurance is appreciated!

On Jul 22, 5:24 pm, Vasil Vangelovski <vvangelov...@gmail.com> wrote:
> I don't think it really matters if one or more processes/threads try
> to access it, when it get's locked EXCLUSIVE for writing only one will
> have access to it until the lock gets released. For a very low volume
> site with very few INSERT/UPDATE/DELETE queries you may not experience
> any difference but if your site grows in the future you'll have to go
> through migrating your data when you have to switch the db, which can
> also be made pretty simple with django.
> If there's a really small ammount of memory on your deployment server
> sqlite might be a better option than something bigger (in that case
> apache is not the best option either, try cherrypy wsgi server). But
> if you have enough resources and the only real reason for using sqlite
> is not wanting to go through db server installation you might want to
> reconsider.
>
>
>
> On Thu, Jul 23, 2009 at 2:02 AM, Some Guy<djul...@gmail.com> wrote:
>
> > Having finished a small app, i'm wondering if it's ok to use sqlite3
> > in a deployment with mod_python and apache.
>
> > I've read that sqlite is not meant for multi-user access where the
> > actual db file is shared, but with several mod_pythons running will it
> > be an issue if they are all having access to it? The site is low
> > volume... should I run 1 max instances of mod_python?
>
> > Is sqlite only meant for development? Django makes it pretty easy to
> > change DBs so don't spare me the harsh truth ! :-)
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to