Timeline for Value of an UNSET NEW.Column in Before Update Trigger
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 4, 2017 at 22:35 | vote | accept | DarbyM | ||
| Feb 3, 2017 at 22:21 | answer | added | a1ex07 | timeline score: 2 | |
| Feb 3, 2017 at 18:40 | answer | added | Rick James | timeline score: 1 | |
| Feb 3, 2017 at 18:24 | comment | added | DarbyM | @a1ex07 Well, that does not yet make sense to me.. but Comparing New to Old when New is not set works. I'm gonna have to assume that if you do not set a column to a value in an update statement, that MySQL sets the NEW.column value = OLD.column value for you.?? So in my case, NEW will always = OLD, UNLESS I set it to something. good answer... Please post it as an answer with a description of why that works, and I will accept it as the answer. | |
| Feb 3, 2017 at 18:09 | history | edited | DarbyM | CC BY-SA 3.0 |
Brief clarification.
|
| Feb 3, 2017 at 18:05 | comment | added | DarbyM | True.. but in the scenario described of updating JUST the UserName.. NEW.Password is not Set/Input/available/or Known. so that would always evaluate to true. | |
| Feb 3, 2017 at 17:56 | comment | added | a1ex07 |
You can compare NEW.Password with OLD.Password, e.g. IF NEW.Password <> OLD.Password THEN
|
|
| Feb 3, 2017 at 17:27 | history | asked | DarbyM | CC BY-SA 3.0 |