> If I'm doing a bulk insert of a very large number of rows > is it possible to add only the ones that don't violate > unique constraints and log the rest?
Yes. - But such functionality depends on some design details. Would you like to invest any software development efforts to get the involved application programming interfaces into the shape that will provide you with enough error information so that you can make the corresponding exception handling really safe, consistent and efficient? > But if there's even 1 row that violates unique constraint > none of the hundreds of non-duplicated rows will get updated either. How much do you need such core database functionality from transaction management? Does each record belong to a change which affects the consistency/integrity for your data structures? Can data updates be really reordered for failure handling? Regards, Markus -- 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 http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
