On 8/27/15 2:12 PM, Demitri Muna wrote:
On Thursday, August 27, 2015 at 1:36:46 PM UTC-4, Michael Bayer wrote:
have you upgraded cx_Oracle to 5.2 lately? An API change was
introduced which corresponds to some users reporting this issue.
The issue is fixed for SQLAlchemy 1.0.9.
No, I'm using PostgreSQL v9.3.9. Sorry, I should have mentioned my
setup. I tested this with
- SQLAlchemy 0.9.6 / psycopg2 2.5.3 / Python 2.7.5
- SQLAlchemy 1.0.8 / psycopg2 2.6.1 / Python 2.7.10
Is 1.0.9 available for download to test (or is this even applicable if
I'm not using Oracle)?
that was a totally cx_Oracle thing that wouldn't apply elsewhere.
So, next thing, has anything changed other than database data? versions
of anything?
Next thing, data-level. If the mapping you have here is to a SELECT or
a join of some kind, if the columns that are the "primary key" come back
as NULL, that won't return an ORM-level entity. Rows with a null
primary key are omitted. echo='debug' would help to illustrate the row
coming back.
Thanks,
Demitri
--
You received this message because you are subscribed to the Google
Groups "sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
To post to this group, send email to [email protected]
<mailto:[email protected]>.
Visit this group at http://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.
