SLUG Mailing List Archives
[SLUG] [OT]: Database Design Question
- To: slug@xxxxxxxxxxx
- Subject: [SLUG] [OT]: Database Design Question
- From: Adam W <adamwoja@xxxxxxxxx>
- Date: Tue, 9 Aug 2005 19:35:11 +1000
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=T+8xaowOMf90oE+tBLgHRyagssm7EmUEBTm59+rZrc4/HEfFrodZEqrjvSgdAFEwfYTgFtPemHLloAtFABTM3GOrRBVnZtTYwqO8MWpwTCt/3xGS1ABTAMnw/160kxGSt45WLql1CMdEgR3rgwrgi9SolRsQ2JCRpyixnSobN0c=
Can anyone put a name to the following type of design...
I need to be able to modify the amount/names of data "fields" stored
for an entity so instead of representing the data stored for an entity
in fields associated with that entity you would relate it to an
another entity which would contain a datafield type field and its
associated value, so different rows in the parent table could possibly
have different datafields associated with it.
The parent table is "person" and it holds common data amongst all
people - it has primary key of personID.
There is another table assoicated with person called "personDetails".
This would have fields "personID", "dataType" and "dataValue". It
might have records like the following:
personID, dataType, dataValue
Of course this is just an example - the parent entity could be anything.
Hope someone can put a name to this sort of design. I want to research
into this to see how people search effectively in this design and its
performance compared to traditional methods etc etc.
Any help would be appreciated.