|
|
Posted by Kenneth Downs on 05/17/06 21:20
Bent Stigsen wrote:
> Kenneth Downs wrote:
>
>>>
>>>> But of course don't take my word for it. Make it a point to try them
>>>> both in your travels, and see which one turns out easier on a system
>>>> that grows over time.
>>>
>>> Just answer this question: Given the original scenario of this thread.
>>> When it is requested for another characteristic to be added, which
>>> design requires less (possibly zero) work to adapt to this new
>>> requirement.
>>>
>>>
>>
>> Mine.
>>
>> Because my tools allow me to change my structures easily, and my
>> framework adapts accordingly.
>
> Well then lets compare worklist.
>
> Here is mine:
> - insert record in table with characteristics.
>
>
> What does your look like?
>
>
> /Bent
How much code will you write to support the new value? Any? Do you know?
How will you propagate your changes from test to production? Will your
collaborators know you did this? Do you have only one customer running
this code or several?
How is the new value documented, do you need to document it?
Are there constraints on allowed values? Does the presence of the new value
affect others columns in other tables?
Do any flags exclude other flags? Do any flags require any other flags?
As I've said now three times in the thread, we don't know, we're just
playing hypotheticals. If and only if none of these questions matters,
than go with your cross-reference, because you are talking about user data
then. (In fact by definition you should not then be doing it, they should
be putting it in). But if even one of them matters than you aren't done
yet.
--
Kenneth Downs
Secure Data Software, Inc.
(Ken)nneth@(Sec)ure(Dat)a(.com)
Navigation:
[Reply to this message]
|