Details
-
New Feature
-
Status: In Testing (View Workflow)
-
Critical
-
Resolution: Unresolved
-
None
-
Q1/2026 Server Development, Q2/2026 Server Maintenance, Q2/2026 Server Development
Description
If we will treat NEW and OLD not as a purely syntactic keywords but as actual row variables of the row type, then one would be able to do
SET NEW=OLD; |
Attachments
Issue Links
- causes
-
MDEV-40124 Assertion `m_sp == m_thd->spcont->m_sp' failed virtual Item *Item_splocal::this_item(), UBSAN : member call on null pointer of type 'Sp_rcontext_handler' in sql/item.cc
-
- In Review
-
-
MDEV-40127 Server hangs when setting NEW=OLD on a multi-row table
-
- In Review
-
-
MDEV-40130 SIGSEGV in Field_iterator_table::set_table at sql/table.h:3350
-
- In Review
-
-
MDEV-40490 SET NEW = (row subquery) in a trigger silently assigns NULL to all columns and skips the single-row check
-
- Open
-
- relates to
-
MDEV-5092 Implement UPDATE with result set (UPDATE ... RETURNING) for single table
-
- Closed
-
-
MDEV-30896 Converting NEW and OLD rows in triggers to JSON
-
- Open
-
- has action item
-
DOCS-6246 Loading...