[MDEV-10916] In trigger's CREATED time microseconds are misinterpreted Created: 2016-09-28  Updated: 2016-09-29  Resolved: 2016-09-29

Status: Closed
Project: MariaDB Server
Component/s: Triggers
Affects Version/s: N/A
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Michael Widenius
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-6112 multiple triggers per table Closed

 Description   

use test;
drop table if exists t1;
create table t1 (i int);
 
SET TIMESTAMP=UNIX_TIMESTAMP('2016-01-01 10:10:10.33');
select now(2);
create or replace trigger tr1 after insert on t1 for each row set @a=@a+1;
 
SET TIMESTAMP=UNIX_TIMESTAMP('2016-01-01 10:10:10.99');
select now(2);
create or replace trigger tr2 after insert on t1 for each row set @a=@a+1;
 
select now(2);
select trigger_name, action_order, created from information_schema.triggers 
  where event_object_table = 't1' and trigger_schema='test';
  
drop table t1;

MariaDB [test]> select trigger_name, action_order, created from information_schema.triggers 
    ->   where event_object_table = 't1' and trigger_schema='test';
+--------------+--------------+------------------------+
| trigger_name | action_order | created                |
+--------------+--------------+------------------------+
| tr1          |            1 | 2016-01-01 10:10:13.30 |
| tr2          |            2 | 2016-01-01 10:10:19.90 |
+--------------+--------------+------------------------+

It looks like microseconds are shifted one position left.



 Comments   
Comment by Michael Widenius [ 2016-09-29 ]

Fixed in development tree. Test case added.

Generated at Thu Feb 08 07:45:54 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.