[MDEV-9500] Bug after upgrade to 10.1.10 (and 10.1.11) Created: 2016-01-31 Updated: 2016-02-23 Resolved: 2016-02-23 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Triggers |
| Affects Version/s: | 10.1.10, 10.1.11, 10.1 |
| Fix Version/s: | 10.1.12 |
| Type: | Bug | Priority: | Major |
| Reporter: | Antonio Fernandes | Assignee: | Sergei Golubchik |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Environment: |
CentOS x86_64 |
||
| Issue Links: |
|
||||||||||||||||
| Sprint: | 10.1.12 | ||||||||||||||||
| Description |
|
Hi Elena and all, The bug behind The Query:
MariaDB 10.1.9: OK 10.1.9 EXPLAIN FORMAT=JSON
10.1.10 and 10.1.11 EXPLAIN FORMAT=JSON
Any idea what might be? Best regards, |
| Comments |
| Comment by Antonio Fernandes [ 2016-02-01 ] | ||||||||||||||||
|
Test with MariaDB 10.1.9 Windows ZIP 64bits: Test with MariaDB 10.1.11 Windows ZIP 64bits: | ||||||||||||||||
| Comment by Elena Stepanova [ 2016-02-01 ] | ||||||||||||||||
|
ampf, | ||||||||||||||||
| Comment by Antonio Fernandes [ 2016-02-02 ] | ||||||||||||||||
|
I've uploaded the tables & trigger 'tbl_stock_grupo_controlo_before_update' (the issue is somehow here). By trial and error I figure it out that, when I delete the trigger, the query runs. When the trigger is enforcing, it throws the error. And with 10.1.9, no issues... | ||||||||||||||||
| Comment by Elena Stepanova [ 2016-02-02 ] | ||||||||||||||||
|
Thanks.I'll check it out shortly. | ||||||||||||||||
| Comment by Elena Stepanova [ 2016-02-03 ] | ||||||||||||||||
|
ampf, thanks for the data, I can reproduce the problem. The problem appeared with the fix for The only two changes: Before running UPDATE, 'root'@'%' needs to be created and granted corresponding permissions, as the trigger has it as a definer. In its absence the problem is still reproducible, but versions which are not affected cannot run the UPDATE when the user is missing. The provided data does not completely correspond the UPDATE from the original description, there is a missing column in WHERE. But it does not affect the outcome, this query does not use the column and still shows the problem:
| ||||||||||||||||
| Comment by Antonio Fernandes [ 2016-02-03 ] | ||||||||||||||||
|
Sorry for that. I've trimmed the data because the 'original' takes 2Gb and I've missed either not removing that columns or removing it from the reported query. | ||||||||||||||||
| Comment by Antonio Fernandes [ 2016-02-23 ] | ||||||||||||||||
|
Any way I can access this build? |