Subject | Re: [firebird-support] design question |
---|---|
Author | Helen Borrie |
Post date | 2004-08-20T08:43:21Z |
At 10:27 AM 20/08/2004 +0200, you wrote:
know what values you're going to want to store in a configuration
table. It's "relationally correct", as well, to store members of paradigms
as rows not columns.
In practical terms, it's a heck of a lot simpler to deploy changes as rows
added to table whose structure never changes, than to deploy a new table
structure each time you add a member to a paradigm...
/helen
>Hi,I prefer this method too. When you first design a system, you simply don't
>
>I'm using the concept
>
>key-column, integercolumn, doublecolumn, datecolumn, stringcolumn
know what values you're going to want to store in a configuration
table. It's "relationally correct", as well, to store members of paradigms
as rows not columns.
In practical terms, it's a heck of a lot simpler to deploy changes as rows
added to table whose structure never changes, than to deploy a new table
structure each time you add a member to a paradigm...
/helen