I'm taking the last piece of DM-16227 - using SQLite's  "ON CONFLICT DO NOTHING" variation of INSERT - out of that ticket because it doesn't work with 3.24 (it does with 3.26), and I'm not totally certain the behavior I'm depending on is guaranteed going forward.

On this ticket, try to answer that question by pestering the SQLite mailing list (etc).  A Stack Overflow question (https://stackoverflow.com/questions/54261493/sqlite-unique-conflict-resolution-ordering) has thus far generated no responses.

An alternative to the current approach would be to instead set the conflict resolution policy at schema definition time.  This works with both SQLite 3.24 and 3.26, but unfortunately is also not clearly documented to do what we want in this case.  If this approach is taken, DM-17154 should be considered a blocker.