Re^5: Migrating database field values rules from Perl code to DB

That's exactly my point. your comment: "Any time you want to start putting application constraints into a database, you should stop thinking and just do the simplest thing possible. That will, most likely, not involve a database." is too general, because it doesn't take into account the fact that in many, MANY, cases the constraints are data (to someone).

Comment on Re^5: Migrating database field values rules from Perl code to DB

Replies are listed 'Best First'.
Re^6: Migrating database field values rules from Perl code to DB by dragonchild (Archbishop) on Feb 13, 2007 at 00:18 UTC
How many CMSes (and similar applications that have user-admins) are created as opposed to standard CRUD / BREAD / reporting applications? My back-of-the-envelope is that it's probably at least 1:1000 and I'm probably underestimating the ratio by at least a couple zeros. Most applications are not meant to be installed, especially ones written in Perl. Furthermore, the need for dynamic configuration is often overestimated. A simple config file that's loaded on startup is good enough for 99% of all configuration needs. My criteria for good software: Does it work? Can someone else come in, make a change, and be reasonably certain no bugs were introduced?	[reply]

Replies are listed 'Best First'.

Re^6: Migrating database field values rules from Perl code to DB
by dragonchild (Archbishop) on Feb 13, 2007 at 00:18 UTC

Furthermore, the need for dynamic configuration is often overestimated. A simple config file that's loaded on startup is good enough for 99% of all configuration needs.

My criteria for good software:

Does it work?
Can someone else come in, make a change, and be reasonably certain no bugs were introduced?

[reply]