> 6. Triggers+family are invisible logic. They can cause confusion during debugging. I'm not sure I can agree. This is the appropriate venue to validate/copy/m

> 6. Triggers+family are invisible logic. They can cause confusion during debugging. I'm not sure I can agree. This is the appropriate venue to validate/copy/mutate data. An heavily constrained table should be documented as a matter of API instructions, because (as you mentioned) they can cause confusion, but let's not throw the baby out with the bathwater, eh?