That's a good point too. I hadn't really thought of that part of it but being able to cover more use-cases with less code certainly does sound helpful. You may end up just moving code around here though, if you were doing certain checks and balances during the rule/view trigger, this would get pushed to the underlying table to enforce security there (not that this is a bad thing admittedly).
I would love to see the performance differences between a system using this, with additional constraints or triggers underneath to maintain necessary data, and a system using the rules system, handling the logic within the rule/trigger on the view.
My experience/projects are a bit unique though, standardization means little to me in my database. I just want awesome features. Nobody, sane at least, has had the late night inspiration to try and port The Schemaverse to Oracle or SQL server.
-Abstrct (AC from parent)