since I don't use UPSERT, I don't have a deep insight on an appropriate API for this, as all the backends have totally different systems, none of which behave the same. Whether a construct would attempt to work "the same" on different backends, or if there are just totally different constructs for each backend, is unknown.
Seems like for PG/MySQL we'd stick to postgresql_on_conflict and mysql_on_duplicate_key. So the actual MERGE statement is nowhere. PG's on_conflict and MySQL's on_duplicate_key still seem quite different. On 01/14/2016 06:27 AM, vmalloc wrote: > Hi, > > Now that Postgres 9.5 is officially out and supports UPSERT (ON > CONFLICT) out of the box - is there any recommended way to use it in > SQLA? Is there any support planned to be added inside the ORM? > > Thanks, > > Rotem > > -- > 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 sqlalchemy+unsubscr...@googlegroups.com > <mailto:sqlalchemy+unsubscr...@googlegroups.com>. > To post to this group, send email to sqlalchemy@googlegroups.com > <mailto:sqlalchemy@googlegroups.com>. > Visit this group at https://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 sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at https://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
