[nycphp-talk] db design/ app logic: making certain rows immutable
David Mintz
david at davidmintz.org
Fri Jul 15 09:55:48 EDT 2011
Pondering how to approach a situation where the application needs to count
on a certain string to be in certain database rows in order to know what to
do. Without going into excruciating detail, let me ask if you think there
are cases where it's good practice to basically hard-code in some rows of a
table certain data that your application needs, and somehow mark them as
immutable -- at the application level, stop the user from touching them.
Other rows in the same table would be fair game -- they can add, modify and
delete.
Comments?
--
David Mintz
http://davidmintz.org/
It ain't over:
http://www.healthcare-now.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nyphp.org/pipermail/talk/attachments/20110715/ebfee3ac/attachment.html>
More information about the talk
mailing list