Since the title of this forum says it is a place for comments about current functionality I’m going to complain about one of my recent issues. When upgrading an xtuple installation from 4.9.5 to 4.11.1 I found that the upgrade process had added a “notifydatachanged” trigger to the database for every file in the DB. Not only in the “public” schema but also in the custom schemas I had added. Even to the standard “pkg…” files that are created when a schema is added via the xtuple updater. I guess my question is “why”. What are the intentions of that trigger to do? Why burden our DB engine with hundreds of triggers that do nothing other than format a string? Was the addition intentional? Just wondering.
Jim