Triggers on Database (table) level.
Before and After
with references (e.g. as Variables) to new and old content for the whole record.
Just like in "normal" databases.
See my idea posted some time ago. They are not exactly the same idea if I understand yours. I wasn't thinking about or interested in having before and after values retained for example. We both want triggers at the table level though.
Can you expand on what problem(s) this would solve for you and give an example or two?
yeah, i saw your idea and voted up.This is the next level, the more normal one, if i have all old/new field values i can do whatever i want, so also on field level.
There are tons of uses, e.g. in another system we use it to keep different databases in sync.Imagine, with such triggers you can easy update even not with ess supported databases (e.g. with MBS on server side).Also a nice place for fixed checks, easy to forget a trigger on one of the 1000 forms several developers maintain in large projects. Here on the central database level ... one trigger on a table to rule them all ;-)
With such triggers you can also get rid of the (for other databases) strange Formular fields, use a real field and do the calculation in a trigger. Makes life with ESS a lot easier.
and so on ....
Sounds good. I added a comment to my idea that gave a little more detail to my request. We are on the same page for sure. Your comment about forgetting to attach a field trigger is part of the issue I had because the database owner had Full Access and would tinker with layouts here and there. They understood that they might break something if they weren't careful, but it was up to me to find and fix all the records in one table that weren't updated because they mucked with the layouts based on another table.
I think this would help a lot to separate business logic from a layout. So "YES".
Retrieving data ...