Unfortunately, no, I could not find a fix for it.
I still suspect some kind of version conflict in the MySQL drivers,
but it's strange, because I even tried creating a new test app, and
django created the database and all the tables just fine. It's only
the admin login that seems to break it.
Hi kinder. I've got this exact problem with django 1.2.3 and python
2.7.
Could you find a fix for it?
On 11 dic, 16:18, Leo wrote:
> Hard to know from what's shown here, but it seems likely that your
> database didn't get created properly on the new server. The error
>
Hard to know from what's shown here, but it seems likely that your
database didn't get created properly on the new server. The error
suggests that the expire_date column of the django_session table in
the MySQL database is of type DECIMAL rather than the expected
DATETIME. How did you migrate
I'm stumped... even removing mod_php from the apache config (which is
where I suspected a different mysql shared library), I still get the
same InvalidOperation error. Any suggestions what to try next?
--
You received this message because you are subscribed to the Google Groups
"Django users"
After some more futzing around this morning, I'm thinking this might
be a shared library version mismatch, maybe with the MySQL client
shared libraries? How can I find out what version django/python is
using?
--
You received this message because you are subscribed to the Google Groups
"Django
At least superficially, it looks like MySQLDB is working ok - a row
does end up inserted in the django_session table. The reason I am
looking in /usr/local/lib/python2.5/site-packages/django/db/models/
query.py around line 317 is because (according to the interactive
stack trace) that is where the
MySQLdb is required to use MySQL with python, so but the error is same as
check to import mysqldb if it working fine, i hope the issue is somewhere
mysqldb settings only.
On Fri, Dec 10, 2010 at 5:58 AM, kinder wrote:
> Ummm... did you mean to say something before the
Ummm... did you mean to say something before the 'for using'? Should I
not use MySQLdb (I'm using version 1.2.2)?
On Dec 9, 5:31 pm, satyandra babu wrote:
> Hi,
>
> for using MySQl with python MySQLdb and it will work fine :)
>
> enjoy coding.
>
>
--
You received this
Hi,
for using MySQl with python MySQLdb and it will work fine :)
enjoy coding.
On Fri, Dec 10, 2010 at 4:48 AM, kinder wrote:
> Hi Dan,
>
> Thanks for taking a look... here's the copy-and-paste stack trace.
>
> ==
>
> Environment:
>
> Request Method: POST
> Request
Hi Dan,
Thanks for taking a look... here's the copy-and-paste stack trace.
==
Environment:
Request Method: POST
Request URL: http://sitename.com/admin/
Django Version: 1.0.4
Python Version: 2.5.5
Installed Applications:
['django.contrib.auth',
'django.contrib.contenttypes',
Hi there,
> I'm fairly new to Django, and I'm trying to move an existing Django
> application to a new server. The old server is running Django 1.0.2
> and Python 2.5.4. The closest I could come on my new server (to start)
> is Django 1.0.4 and Python 2.5.5.
>
> Anyway, I get an admin login
I'm fairly new to Django, and I'm trying to move an existing Django
application to a new server. The old server is running Django 1.0.2
and Python 2.5.4. The closest I could come on my new server (to start)
is Django 1.0.4 and Python 2.5.5.
Anyway, I get an admin login screen, but when I try to
12 matches
Mail list logo