Hi Michael,
It did not happen every time. I'm pretty sure with 0.8.x it did not happen.
show standard_conforming_strings -- on
About the Exception...
Could it be this one?: AttributeError('module' object has no attribute
'ps2',)
Thank you very much!
Pau.
2014-05-30 22:26 GMT+02:00 Michael
Or this one:
(Pdb) p cursor.close()
*** InternalError: InternalError('current transaction is aborted, commands
ignored until end of transaction block\n',)
2014-06-02 14:15 GMT+02:00 Pau Tallada tall...@pic.es:
Hi Michael,
It did not happen every time. I'm pretty sure with 0.8.x it did not
I have no idea what that error is. Seems like something local to your
application.
On Jun 2, 2014, at 8:15 AM, Pau Tallada tall...@pic.es wrote:
Hi Michael,
It did not happen every time. I'm pretty sure with 0.8.x it did not happen.
show standard_conforming_strings -- on
About the
OK, anyway, the issue is fixed so that particular error (which is very common
in PG after an error has occurred) will just be a warning.
On Jun 2, 2014, at 8:26 AM, Pau Tallada tall...@pic.es wrote:
Or this one:
(Pdb) p cursor.close()
*** InternalError: InternalError('current transaction is
Hi,
I don't know if I am doing something wrong :/
It also happens if instead of *engine.connect().connection* I use
*engine.raw_connection*.
But I think that the error dissappears if you use a standard connection
of something like that.
There has to be some side effect, because when I run this
is that happening every time? it's a bug where an exception is raised on
connect but it's not being allowed to display. Can you please invoke the
statement show standard_conforming_strings on your connection and/or
Postgresql database so I can see what it's saying?
On May 30, 2014, at
The exception here is fixed in master, rel_1_0 and rel_0_9 branches, it is
https://bitbucket.org/zzzeek/sqlalchemy/issue/3063/engine-base-safe_close_cursor-assumes-our.
That is, it won't choke trying to log the cursor close error.But there's
still an error that was raised here when this
