I'm trying to run syncdb on a clean database (no other tables etc.) in postgres. It produces the standard Postgres error:
psycopg2.ProgrammingError: current transaction is aborted, commands ignored until end of transaction block Digging a bit deeper, I see the exception is thrown in get_table_list (django/core/db/backends/postgres_psycopg/introspection.py) Specifically, line 14: return [row[0] for row in cursor.fetchall()] causes the following exception to be raised: psycopg2.ProgrammingError: no results to fetch The fact that there are no results to fetch makes sense since there are no existing relations (table) in the database, but why this is causing an exception is strange. Wouldn't any new database installation not have any results to fetch? I know there's nothing wrong with my settings file and/or models code because I'm just trying to clone an already-working instance from another server. Has anybody seen this before? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
