On Tuesday, September 27, 2016 at 12:54:47 PM UTC-7, Jeremy Evans wrote: > > On Tuesday, September 27, 2016 at 12:50:37 PM UTC-7, > [email protected] wrote: >> >> Hi, >> >> I noticed that doing >> >> *DB[:table].insert_conflict(update: >> hash_of_update_values}).multi_insert(array_of_hashes)* >> >> does not add the ON CONFLICT DO UPDATE clause to my insert query. >> >> Am I doing something wrong? Is this a known issue? Could I some help >> please? >> > > This looks like an implementation issue which should be relatively easy to > fix. I'll try to fix it before the next release. >
Actually, after doing some testing, it looks like this is already handled correctly. I added a spec for the behavior: https://github.com/jeremyevans/sequel/commit/6e9a63fda02c5817c4ea1de951e44ee0d926e812 If you think it isn't working correctly, please provide a small self-contained example showing the problem (or a failing spec) and I will look into it. Thanks, Jeremy -- You received this message because you are subscribed to the Google Groups "sequel-talk" 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 https://groups.google.com/group/sequel-talk. For more options, visit https://groups.google.com/d/optout.
