I think I fully understand the old saying of "no single leave is the
same", different database would have different structure / schema for
different business need(s), along the line, data update (including
insert, update and delete) for a particular database may be restricted
to a group of users, and possibly, of them, some have the full
privilege of "update" while others may not have the privilege of
delete.

Would this understanding, common practice exclude the value or the use
of re-usable component? On the other hand, we know all the data in a
given database needs to be updated at some point except the storage of
historical data and fact data, for instance, "Mexico is to the south
of USA" as a piece of fact. Which means, functions for data insert,
update and delete is definitely necessary for most business processes,
so, why would we write code like

insert into tableA (colInt1,colChar2)
values (1,'ab');

insert into tableB (colInt1,colVar3)
values (1,'abc');

.... exp N

instead of something like

-- using a re-usable component
insert into tblVar(col1Var, col2Var ...)
values (v1,v2 ...)

Yes, I understand some CASE / designing tool has the feature to create
sps during database generation process. But since no standard for
doing this, appplication developer would have to figure out the
pattern of sps created by each of these tool, then call sp where
appropriate. Still quite involved.

Here is my approach, what do you think? btw, user roles can be easily
configured. URL, http://68.32.61.40/datadata/DataMan.cfm


Thanks.

Li, Chunshen (Don)