Re: Database Design Pattern Question (help!)

[...]
> TABLE
> ---------
> TableId
> Ticker
> quantity
> Currency
> Price
> MarketValue
>
>
> TABLE_DETAIL
> ---------
> TableDetailId
> *TableId <---------------- Foreign Key
> Key <---------------- Indexed
> Value <---------------- Will be a Varchar(100)
>
>
> example data:

[...]

Yes i understand the point...

my two euro-cents

consider that in this situation you might have the same datatype vc2 for different domains, this is evidently incorrect from a logical point of view.
However i had the same problem few years ago designing a model for a banking application. Toghether with the developer guy we agreed and came to a solution: gathering attributes in entities related one to one to the main entity... eg: the main entity is "companies" and everything related to the company assets went to one differnt table "Assets" and so on... The GUI reflected this design... there were a tabbed form where the users everytime switched from a tab to another a query was performed against the database with a primary key value...

/G Received on Fri Oct 03 2003 - 17:37:54 CDT