add allow_null_pks to your mapper arguments
See
http://www.sqlalchemy.org/docs/05/reference/orm/mapping.html
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group, send email to
thanks a lot mike, it's working great now.
but this flag should be implied if one of the primary key fields is nullable
(especially since it's not nullable by default).
what would you think?
On Thu, Oct 15, 2009 at 14:28, Mike Conley mconl...@gmail.com wrote:
add allow_null_pks to your
On Thu, Oct 15, 2009 at 9:21 AM, alexbodn.gro...@gmail.com wrote:
thanks a lot mike, it's working great now.
but this flag should be implied if one of the primary key fields is
nullable (especially since it's not nullable by default).
what would you think?
You can argue just as easily
-Original Message-
From: sqlalchemy@googlegroups.com
[mailto:sqlalch...@googlegroups.com] On Behalf Of Mike Conley
Sent: 15 October 2009 14:43
To: sqlalchemy@googlegroups.com
Cc: SQLElixir
Subject: [sqlalchemy] Re: bad result when querying for null
values (in pk at least)
On Thu, Oct 15, 2009 at 15:43, Mike Conley mconl...@gmail.com wrote:
On Thu, Oct 15, 2009 at 9:21 AM, alexbodn.gro...@gmail.com wrote:
thanks a lot mike, it's working great now.
but this flag should be implied if one of the primary key fields is
nullable (especially since it's not nullable
On Thu, Oct 15, 2009 at 15:48, King Simon-NFHD78 simon.k...@motorola.com
wrote:
-Original Message-
From: sqlalchemy@googlegroups.com
[mailto:sqlalch...@googlegroups.com] On Behalf Of Mike Conley
Sent: 15 October 2009 14:43
To: sqlalchemy@googlegroups.com
Cc: SQLElixir
Subject:
