Thank you! I can confirm it works.
On Tuesday, 11 November 2014 17:36:24 UTC, Michael Bayer wrote:
this is fixed for 0.9.9 which you can get from git right now.
On Nov 11, 2014, at 10:53 AM, Michael Bayer mik...@zzzcomputing.com
javascript: wrote:
Hello,
I've been trying to insert a row based on a correlated subquery that
returns a UUID. The insert query itself returns a long, which somehow
SQLAlchemy tries to process as a UUID/GUID.
I'm using SQLAlchemy 0.9.8, Psycopg2 2.5.4 and PostgreSQL 9.1.
Here is an example that demonstrates
https://bitbucket.org/zzzeek/sqlalchemy/issue/3248/populate_result_map-gets-set-for-select
https://bitbucket.org/zzzeek/sqlalchemy/issue/3248/populate_result_map-gets-set-for-select
, will be most likely fixed today.
On Nov 11, 2014, at 10:18 AM, Bruno br...@distributedmatter.net wrote:
this is fixed for 0.9.9 which you can get from git right now.
On Nov 11, 2014, at 10:53 AM, Michael Bayer mike...@zzzcomputing.com wrote:
https://bitbucket.org/zzzeek/sqlalchemy/issue/3248/populate_result_map-gets-set-for-select
