And for anyone searching this:
http://www.djangoproject.com/documentation/django_admin/#sqlsequencereset-appname-appname
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group,
HURRAY I fixed it.
For the record, this was my problem - no bug in Django.
I have imported semi-automatically some values from a previous version
of my app. I had to use the same Primary keys in order to keep all the
relations. However, I didn't adjusted the postgres sequences, so they
tried
I get this back:
[{'sql': 'SELECT
"django_session"."session_key","django_session"."session_data","django_session"."expire_date"
FROM "django_session" WHERE ("django_session"."session_key" =
d3b9c68e8d397b3fc0809ce5102e0299 AND "django_session"."expire_date" >
2006-11-05 13:39:36.338000)', 'time':
On 11/4/06, orestis <[EMAIL PROTECTED]> wrote:
...
> cursor.execute("SET TIME ZONE %s", [settings.TIME_ZONE])
> ProgrammingError: ERROR: current transaction is aborted, commands
> ignored until end of transaction block
>
> SET TIME ZONE 'Europe/Athens'
> }}}
...
This error is reported by pos
I got this ticket rejected from Akismet:
This is not related to #852, as the errors are thrown when running the
application normally, not the shell.
The errors I get are:
{{{
File "/usr/lib/python2.4/site-packages/django/db/models/base.py",
line 166, in save
cursor = connection.cursor()
5 matches
Mail list logo
