On Tue, 2009-02-10 at 16:22 -0800, lazyant wrote: > Thanks a lot Jeff. > > I figured out the problem which was a bit more complicated than that > but basically was also what you said. > > I downloaded the sqlite3 client and that helped too. > > What throw me off (among other things) is that in Linux you only need > executable permissions to a directory and write permissions to a file > to modify it and for apache/sqlite3 you also need write permissions to > the directory, not sure why and especially since the other files > (owned by root, in the same directory) are accessed by apache without > problems and no temporary files etc are created.
Well, that last part isn't necessarily true: http://www.sqlite.org/tempfiles.html > > Also the examples and solutions from people in the web where they gave > all kinds of permissions to the main code directory (where the > database file was) and file didn't make sense to me from a security > standpoint; I think a better solution is to put the sqlite file in a > separate directory (just for that file), that way we don't have to > lower the security of the rest of the project. That would make sense in general, anyway. The code is generally a stable entity and developed independently from the database content. So, for example, you are unlikely to version control your database, whereas you might well back-up the database under a different regime to the code (since the former changes more regularly and is non-recoverable in a lot of situations, whereas the code is possibly under version-control and changes less often). Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
