Well, maybe there's more to it than I wrote originally.

I imagine a Perl script with some generic form generation routines that take their directions from some specs held within the database.

For example, for field_1:

• at creation is to be displayed as a drop-down on the creation screen, with possible values a-to-z,
• not be editable on a record-update screen
• in a listing of records from the table, not be displayed if the user is of user_type=X.

These parts of the database specification are going to be littered here and there throughout the system, in conditionals and template layouts. What I imagine is having these specs centralized within the database somewhere and then a generic screen form element generator script that takes its direction from those specs.

Mmmmmm....I'm beginning to imagine a table of table column specs.....

Table: specs
table_name, field_name, creation_form_type, editable, view_types,....
[download]

Something like that....but I fear a great deal of querying for every page generation.

---

In reply to Re: Migrating database field values rules from Perl code to DB by punch_card_don
in thread Migrating database field values rules from Perl code to DB by punch_card_don

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.