On Tue, Nov 03, 2009 at 16:29 -0500, Michael Bayer wrote: > the error is raised directly by psycopg2.
I was afraid that the error is with psycopg2. Are you aware of any
bugtracker, mailing list or IRC channel that discusses psycopg2?
> I'd try taking out the ";" at the end of the statement,
That did not help unfortunately. Can you think of anything else I might
try?
The error does not occur with all INSERT statements I read from the
dump files, so I think that the problem is with the actual
string/statement. Why does psycopg2 not hand the statement to PostgreSQL
unaltered? Can I force that somehow?
I think i might just open a subprocess directly to psql to execute these
statements. At least I will not have to bother with bugs not caused by
me.
> and also checking against a literal string to
> see if something weird is happening when you read the file.
I don't think that anything weird happens when I am reading the file,
but testing this is nearly impossible, as the statement is rather huge.
thanks for the help
Wolodja
signature.asc
Description: Digital signature
