I am setting up a database trigger to track a date change on a database object (ticket).
The trigger should go of when ticket before’s s SLA Date Extract Unix is not ticket now’s SLA Date Extract Unix
(I tried the same with using a formatted as instead of extract unix with the same results).
Here I create a simple text log to test the logic:
Weirdly though, the date before and after is the same according to the evaluation:
The date absolutely changed though.
I am puzzled to the max here. 
Edit: After testing it does not trigger because the change is already triggered by another database event. I am thinking Bubble must have some db trigger to db trigger blockade to prevent recursive changes. When chaning the value from input or database the trigger works as expected.
