Re: Replaceing records

> You can do
>  INSERT INTO tab (...) VALUES (...) ON DUPLICATE KEY UPDATE col=val, ...

This would allow making sure insert won't throw exceptions on unique
constraint violations. Good enough to avoid breaking transactions.

>
> But I'm not sure how convinced the developers are of its usefulness beyond
> satisfying mysql migrations. I've never used mysql and I have seen a few times
> it might have been useful. Not a lot, but a few. And it seems to be a frequent
> question on the mailing list.

If nested transactions is easier to implement, that would be better.
Covers more of the current problems.

Cheers,
Csaba.