Re: [sqlalchemy] Re: bad result when querying for null values (in pk at least)

0 views
Skip to first unread message

alexbod...@gmail.com

unread,
Oct 15, 2009, 9:21:57 AM10/15/09
to sqlal...@googlegroups.com, SQLElixir
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 <mcon...@gmail.com> wrote:
> 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 sqlal...@googlegroups.com
> To unsubscribe from this group, send email to
> sqlalchemy+...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/sqlalchemy?hl=en
> -~----------~----~----~----~------~----~------~--~---
>
>



--
alex

Reply all
Reply to author
Forward
0 new messages