I did this all, but it still doens't work :(
When running ./dispatch.fcgi directly it looks as though the problem
is all cleared up, but even after killing fcgi 'till it's dead it
still brings up a 500 error on my site.
Does this sound like it's still related or is it some other problem?
If it i
On 3/21/07, worksology <[EMAIL PROTECTED]> wrote:
>
> I have the exact same issue, also with Dreamhost. I tried the
> "mysql_old" thing, but still got the same error.
Malcolm has just checked in a fix.
this has saved My_old backend :)
Derek
--~--~-~--~~~---~--~--
I'm guessing that the import statement in mysql_old/introspection.py
should read:
from django.db.backends.mysql_old.base import quote_name
rather than:
from django.db.backends.mysql.base import quote_name
That seems to have worked for me, but probably should be fixed in the
source, eh?
- Josh
I have the exact same issue, also with Dreamhost. I tried the
"mysql_old" thing, but still got the same error. Here's the relevant
part of the stack trace:
File "/django_src/django/db/backends/mysql_old/introspection.py",
line 1, in ?
from django.db.backends.mysql.base import quote_name
On Wed, Mar 21, Adam wrote:
>
> This causes a problem with DreamHost...I know they're not the best in
> the world, but I get this error now on any sites on their servers.
> Does anyone have a decent solution to get around this? Can I install
> a local copy somehow and make django use it instead
This causes a problem with DreamHost...I know they're not the best in
the world, but I get this error now on any sites on their servers.
Does anyone have a decent solution to get around this? Can I install
a local copy somehow and make django use it instead of their version?
Has anyone had luck g
On 3/20/07, chasfs <[EMAIL PROTECTED]> wrote:
>
> Thanks for the quick reply! Do you know if Django has been tested
> with MySQLdb
> 1.2.2?
Yes. 1.2.2 is the best version you can get. Trust me.
> On Mar 20, 11:20 am, "James Bennett" <[EMAIL PROTECTED]> wrote:
> > On 3/20/07, chasfs <[EMAIL PROT
Thanks for the quick reply! Do you know if Django has been tested
with MySQLdb
1.2.2?
On Mar 20, 11:20 am, "James Bennett" <[EMAIL PROTECTED]> wrote:
> On 3/20/07, chasfs <[EMAIL PROTECTED]> wrote:
>
> > The problem is that the MySQLdb page says that 1.2.1p2 has no changes
> > that we should wor
On 3/20/07, chasfs <[EMAIL PROTECTED]> wrote:
> The problem is that the MySQLdb page says that 1.2.1p2 has no changes
> that we should worry about. Why is p2 required?
Unfortunately, there is a change that we need to worry about: the
thread-safety bug in MySQLdb which caused ticket #3279[1] wasn
9 matches
Mail list logo
