On 3/10/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Ok, thanks. Now it solved. I am moving the database file to a
> directory that writable to others and change the database file
> permission to be writable by others. But I think it will be a security
> issue. What do you suggest?
If you'
Ok, thanks. Now it solved. I am moving the database file to a
directory that writable to others and change the database file
permission to be writable by others. But I think it will be a security
issue. What do you suggest?
regards,
On Mar 11, 8:22 am, "James Bennett" <[EMAIL PROTECTED]> wrote:
On 3/10/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> do you mean that the directory and file of SQLite database file shall
> be able to be written by Apache?
Yes. TO use SQLite under Apache/mod_python, the SQLite database must
be readable and writable by the user Apache is running as. Wheth
ble by all' directory such as /tmp ?
thanks and best regards,
On Mar 11, 6:17 am, "James Bennett" <[EMAIL PROTECTED]> wrote:
> On 3/10/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> > OperationalError: Unable to close due to unfinalised statements
>
> U
On 3/10/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> OperationalError: Unable to close due to unfinalised statements
Usually this means that there's a permissions issue with SQLite. This
often pops up when switching from the development server to Apache,
because on hosting s
66, in close
self.connection.close()
OperationalError: Unable to close due to unfinalised statements
My urls.py
from django.conf.urls.defaults import *
urlpatterns = patterns('',
# Example:
# (r'^mysite/', include('mysite.apps.foo.urls.foo')),
6 matches
Mail list logo
