Re: Transpose query results?
From: khalprin (khalprin_at_discussions.microsoft.com)
Date: 12/22/04
- Next message: John Bell: "Re: Porting of Oracle cursor structure in T-SQL"
- Previous message: Bob Barrows [MVP]: "Re: Select * where 1 = 1"
- In reply to: --CELKO--: "Re: Transpose query results?"
- Next in thread: Anith Sen: "Re: Transpose query results?"
- Reply: Anith Sen: "Re: Transpose query results?"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 22 Dec 2004 08:57:01 -0800
Thanks for your wonderful help.
I'll worry about why the data is stored as it is - that is not currently the
issue. Describing the way the data needs to be presented in the end result
provides more information to solve the problem... for those willing to help.
"--CELKO--" wrote:
> This design flaw is called EAV (Entity-Attribute-Value) in the
> literature. It comes from not separating data and metadata.
>
> >> This has a record for each configurable property <<
>
> Rows are not records; attributes are not properties. You are not even
> speaking in relational terms.
>
> >> I need to use the records [sic] from the 'Properties' table as the
> columns in a grid and display the values <<
>
> SQL has nothing to do with display; in a tiered architecture the front
> end does display. You are not separating the presentation layer.
>
> You might want to read at least one book on RDBMS and one on data
> modeling and start over.
>
>
- Next message: John Bell: "Re: Porting of Oracle cursor structure in T-SQL"
- Previous message: Bob Barrows [MVP]: "Re: Select * where 1 = 1"
- In reply to: --CELKO--: "Re: Transpose query results?"
- Next in thread: Anith Sen: "Re: Transpose query results?"
- Reply: Anith Sen: "Re: Transpose query results?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|