in reply to Re^3: Migrating database field values rules from Perl code to DB
in thread Migrating database field values rules from Perl code to DB

That's an apples'n'oranges distinction. "administrators" of a CMS are users of that CMS. The developers are meeting their user requirements.
My criteria for good software:
  1. Does it work?
  2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?
  • Comment on Re^4: Migrating database field values rules from Perl code to DB

Replies are listed 'Best First'.
Re^5: Migrating database field values rules from Perl code to DB
by hossman (Prior) on Feb 12, 2007 at 22:24 UTC

    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).

[reply]
      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:
      1. Does it work?
      2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?
[reply]

In Section Seekers of Perl Wisdom