2009-11-03 19:10:04 UTC
As I understand it, the essence of the argument is:
> Both are changing the database without leaving log on Adempiere change log (a very undesirable effect and precisely the reason why database triggers are not recommended)
and such a behavior is in the essence of the SQL specification, rather than anything within ADempiere's control.
What is in ADempiere's control is the logging it emiis -- Rather than hobble SQL expressiveness, why not adopt a coding standard to suggest running the query with an 'explain' keyword (MySQL) or such, and do better logfile messages on the expected behaviors.
But at the end of the day, the only authoritative is the sources, and not comments and commentary on the sources. Flagging such traps and pitfalls in the sources is not something that anyone would oppose, I think.
as such: -1
I am against a proposal: drop all cascade constraints in DB
-- Russ herrold
