Changes between Initial Version and Version 1 of Ticket #35793, comment 9


Ignore:
Timestamp:
Aug 21, 2025, 1:41:53 PM (2 weeks ago)
Author:
Take Weiland

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #35793, comment 9

    initial v1  
    33
    44- All supported DBs (all except Oracle, for which `update_conflicts` is not implemented) support referring to the values that were about to be inserted.
    5 - PostgreSQL and SQLite explicitly state support for referring to the row that is conflicting and that will be  updated (www.postgresql.org/docs/current/sql-insert.html, https://sqlite.org/lang_upsert.html)
     5- PostgreSQL and SQLite explicitly state support for referring to the row that is conflicting and that will be  updated (https://www.postgresql.org/docs/current/sql-insert.html, https://sqlite.org/lang_upsert.html)
    66- MySQL does not state such support, however their examples show it being done (`ON DUPLICATE KEY UPDATE c=c+1;` from https://dev.mysql.com/doc/refman/9.4/en/insert-on-duplicate.html)
    77- MariaDB does not state such support, however considering it started from MySQL I would be surprised if it is not supported.
Back to Top