Do nothing on DEDUP UPSERT about questdb HOT 5 OPEN

I suggest we also do an UPSERT MERGE i.e like a PATCH.

So based on the above syntax, it could be something like:

ON CONFLICT DO REPLACE (default, don't need to specify but can if you choose )

ON CONFLICT DO NOTHING (skip rows)

ON CONFLICT DO MERGE (merge new values into old row)

from questdb.

Upvoted. This would be quite key to my project as well, thanks a lot for looking into this!

from questdb.

also Interested!

from questdb.

scheduling

from questdb.

Upvoted - this would be a very useful feature for some of the datasets we store at my day job

from questdb.