[nycphp-talk] db design/ app logic: making certain rows immutable
federico ulfo
rainelemental at gmail.com
Fri Jul 15 10:06:20 EDT 2011
Yes, is called permission and it make sense, same as file system there can
be users that have limited access on some contents
Sent from my iPhone
On Jul 15, 2011, at 9:55 AM, David Mintz <david at davidmintz.org> wrote:
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/
_______________________________________________
New York PHP Users Group Community Talk Mailing List
http://lists.nyphp.org/mailman/listinfo/talk
http://www.nyphp.org/Show-Participation
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nyphp.org/pipermail/talk/attachments/20110715/b369bd64/attachment.html>
More information about the talk
mailing list