Hi!
I have downgraded my pysqlite version from 2.3.1 (or 2.3.2, I tried
first this upgrade, but with same errors like in 2.3.1) to 2.0.7, and
it worked again. My trac installations behave similar, so I think it is
a problem with the newer pysqlite versions.
Best regards,
Ralf
--~--~---
Malcolm Tredinnick wrote:
> The way Django handles database connections with sqlite doesn't appear
> to be entirely threadsafe for some subtle reason. The short version is
> that you cannot use mod_python and sqlite together reliably at the
> moment.
Thanks. I already started to think that porti
On Sun, 2006-10-22 at 19:42 +, anna wrote:
[...]
> AttributeError: 'str' object has no attribute 'close'
> #end error
[...]
> When I changed to mysql, everything worked fine, so nothing is wrong
> with the installation itself.
>
> I appreciate any ideas.
The way Django handles database conn
Baczek wrote:
> A common problem is that even though the db file is writeable, the
> directory it's in isn't, and it has to be because sqlite needs to make
> a logfile there.
Thanks, I checked that, I even made an installation where I did a chmod
-R 777 myprojectdir. And I put the database file
Hi,
I am trying to move a django application from one server another. The
old server is a Fedora Core 4 server with python-2.4.3, mod_python-3.1
and sqlite-3.1. The new server is CentOS 4.4 (AMD64). This server is
depends on a python 2.3 rpm. As I understand it, it is discouraged to
upgrade the
A common problem is that even though the db file is writeable, the
directory it's in isn't, and it has to be because sqlite needs to make
a logfile there.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django user
6 matches
Mail list logo
