Proposal: ignore_conflict about moebius HOT 3 OPEN

Hi @bunnylushington - could provide some hypothetical scenario? How are you using this?

from moebius.

Sure. In a couple of instances in my code I'm receiving bursts of data where checking for the presence of an existing record would cause more DB traffic than is ideal and ignoring dups is sufficient. I am, however, interested in capturing any errors where other constraints are not fulfilled. In my code (minus any error handling) that's something like:

    {:ok, _} = Query.db(:messages)
    |> Query.insert(message)
    |> ignore_conflict(:message_id)
    |> Moebius.Db.run()

where message_id is my PK. I do something functionally similar with (reasonably small) lookup tables where new entries may be created but existing rows are immutable. There are more defensive ways of coding for that but this happy path approach where everything is inserted (or ignored) each time it's refreshed is easy to maintain and reason about.

To be clear: it's not a problem if this is inappropriate for inclusion! I use this pattern a lot but understand that I might be so very alone. 😄

from moebius.

That sounds useful, I'm open to a PR as long as it's well tested :)

from moebius.