On 8/16/23 12:01, Rob Sargent wrote:
On 8/16/23 12:30, Guyren Howe wrote:
For some reason, I was thinking the rule could see just the fields
from the command, but you’re right; a rule won’t work. Sorry.
Guyren G Howe
On Aug 15, 2023 at 23:22 -0700, Russell Rose | Passfield Data Systems
<russellrose@xxxxxxxxxxxxxxx>, wrote:
I have just had a quick look at rules and I am not sure how it can be
done. Rules still use the concept of NEW and OLD. If my original row
has 'myfield' set to 'me' then I don't think I can tell the
difference between:
Update mytable set afield='something'
and
Update mytable set afield='something',myfield='me'
Within the rule I think NEW.myfield will be set to 'me' in both
cases. Please can you explain how I can tell the difference between
the two update statements
If the original value in the user column is "me", what is the difference
between "set other_column = some_value, user = 'me'" and "set
other_column = some_value" at the business level?
Affirmation that the user updating the record explicitly set the user value.
--
Adrian Klaver
adrian.klaver@xxxxxxxxxxx
