Cabrion:

I've done the same technique a few times. I used Sybase for one, and MS SQL for another. It's a very nice technique. I also like to remove permissions from the underlying objects where possible. Then, every time I get to modify one of the client apps, I fix 'em, and try removing more permissions & such.

The only problem with such an incremental approach is that you often don't finish. (I've got one in a rather odd state right now.) Then if you have to turn over the project to someone else, they may be confused by it. Hopefully, they have a well-developed sense of "taste" and will continue the migration towards a rational end.

On my last project, I was the fourth person to work on it. You could plainly see that each one had their own philosophy. I didn't want a fifth philosophy in the code, so I just adopted the one that the majority of the code used. As for the database, it was just a bunch of tables. No relationships at all! Needless to say, I started tying things together in there. Another release or two, and at least the database will be in good shape. (Heaven help the code, though....)

--roboticus

In reply to Re^2: Creating a model of a bad database by roboticus
in thread Creating a model of a bad database by Ovid

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


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.