Search Results
Search type | Search syntax |
---|---|
Tags | [tag] |
Exact | "words here" |
Author |
user:1234 user:me (yours) |
Score |
score:3 (3+) score:0 (none) |
Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
Views | views:250 |
Code | code:"if (foo != bar)" |
Sections |
title:apples body:"apples oranges" |
URL | url:"*.example.com" |
Saves | in:saves |
Status |
closed:yes duplicate:no migrated:no wiki:no |
Types |
is:question is:answer |
Exclude |
-[tag] -apples |
For more details on advanced search visit our help page |
Procedural code automatically executed in response to a database event.
1
vote
1
answer
72
views
Weird behaviour with batch and trigger(MariaDB)
CREATE DEFINER=`USERADMIN`@`%` TRIGGER `TRG_BU_T_INSTANCE`. … BEFORE UPDATE ON `t_instance` FOR EACH ROW BEGIN
SET NEW.ATTRCHANGEID=UUID();
END
TRIGGER (AFTER UPDATE)
CREATE DEFINER=`USERADMIN`@`%` TRIGGER `TRG_AU_T_INSTANCETEST` AFTER UPDATE ON `t_instancetest …
0
votes
Accepted
Weird behaviour with batch and trigger(MariaDB)
CONJ-1086
which also affects batch update.
the issue is also found by some other people eg :
https://stackoverflow.com/questions/76430213/jooqs-batchinsert-doesnt-behave-as-expected-with-after-insert-trigger … Some points :
Issue happened since MariaDB has implemented a new bulk processing mode , together with new jdbc4.2
however this new bulk processing has an issue where combined with trigger ( after update …