More on MySQL and Django problems
I complained about instability of this site in my previous post. Now, after intensive googling, it looks like it may be related to multiple threads or forked processes using the same connection to MySQL. Apparently it can confuse MySQL. Children should create their own connections after spawning.
If Django does reuse connections, it may be possible to fix it. Otherwise, CGI is the way to go. The latter solution would be slow.
Save/recommend this post:
Subscribe to this blog:
Most recent related documents:
Documents published at about the same time:
- Something wrong with simple cache — September 9, 2005
- Say no more! Say no more! — September 8, 2005
- Django on Dreamhost: happy end — September 7, 2005
- Django with MySQL: problem solved? — September 5, 2005
- Opera and Dojo — September 5, 2005
- Django and MySQLdb worries — September 4, 2005
- Dojo: 1st impression — September 3, 2005
- New Design 0.1 is here! — September 2, 2005
