Re: [sqlalchemy] on_conflict_do_update (ON CONFLICT ... Postgresql 9.5) WHERE clause problem

2016-09-29 Thread Mike Bayer
I just pushed that and it should close the bitbucket issue. On 09/29/2016 03:07 AM, pszynk wrote: I see you already looked into it. Thanks! W dniu środa, 28 września 2016 20:55:05 UTC+2 użytkownik Mike Bayer napisał: this is likely use cases that have been untested, if you can file this

Re: [sqlalchemy] on_conflict_do_update (ON CONFLICT ... Postgresql 9.5) WHERE clause problem

2016-09-29 Thread pszynk
I see you already looked into it. Thanks! W dniu środa, 28 września 2016 20:55:05 UTC+2 użytkownik Mike Bayer napisał: > > this is likely use cases that have been untested, if you can file this > w/ a complete test case as a bug report on bitbucket we can start > looking into it. > > > On

Re: [sqlalchemy] on_conflict_do_update (ON CONFLICT ... Postgresql 9.5) WHERE clause problem

2016-09-28 Thread Mike Bayer
this is likely use cases that have been untested, if you can file this w/ a complete test case as a bug report on bitbucket we can start looking into it. On 09/28/2016 12:05 PM, Paweł Szynkiewicz wrote: Hello all SA: 1.1.0b3 db: postgresql 9.5 I have a problem with method

[sqlalchemy] on_conflict_do_update (ON CONFLICT ... Postgresql 9.5) WHERE clause problem

2016-09-28 Thread Paweł Szynkiewicz
Hello all SA: 1.1.0b3 db: postgresql 9.5 I have a problem with method on_conflict_do_update for pg specific insert. Precisely with the where argument. It looks like wrong SQL statement is generated. example: class Foo(Base): ... bar = Column(Integer) insert_stmt = insert(Foo)