Re: OperationalError: unable to open database file, when saving existing object

2009-10-04 Thread pigmalione
For what it's worth, I found some kind of solution. Apparently, running under a user administrator account in Windows causes this kind of permissioning issue. If I enable the windows hidden administrator and work under that account, this issue disappears. A bit annoying. --~--~-~--~~-

Re: OperationalError: unable to open database file, when saving existing object

2009-10-01 Thread pigmalione
Hi, Wim - Thanks a lot for the reply. I'm doing everything through code, since accessing the admin interface is itself plagued with issues. And as far as I can tell, I am the same user as the owner of the db-file (since I can also change privileges on the file at will). These are some more sympt

Re: OperationalError: unable to open database file, when saving existing object

2009-09-27 Thread Wim Feijen
So, if I understand correctly, creating new objects and saving them to the database works correctly, and updating objects fails. Is that correct? Is it an update from the admin interface or from code written by you? If the former, it might have something to do with db privileges. Which back-end a

OperationalError: unable to open database file, when saving existing object

2009-09-27 Thread pigmalione
Hello, When I attempt to save an existing db object I get the following error: File "", line 1, in File "/usr/lib/python2.5/site-packages/django/db/models/base.py", line 410, in save self.save_base(force_insert=force_insert, force_update=force_update) File "/usr/lib/python2.5/site-pa