Re: Bizarre sqlite3 / apache2 behaviour

2009-02-11 Thread Malcolm Tredinnick
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

Re: Bizarre sqlite3 / apache2 behaviour

2009-02-10 Thread lazyant
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

Re: Bizarre sqlite3 / apache2 behaviour

2009-02-10 Thread Jeff FW
You need to make sure that the user apache is running as (usually "apache") has write access to the database file *and* the directory that the database file is in. The development server would work because *you* probably have write access to those paths. As for the sqlite3 version, run python,

Bizarre sqlite3 / apache2 behaviour

2009-02-09 Thread lazyant
Hello, I installed yesterday Django 1.0.2 (current downloadable version) on a new Ubuntu 8.10 machine with python 2.5.2. I wrote a toy application and it works and shows fine with both the built-in development server and Apache 2 (2.2.9). The database is sqlite3, it came with python (btw, how do