Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase «««123

Name Value Pair - Part II Expand / Collapse
Author
Message
Posted Tuesday, May 20, 2008 1:27 PM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Monday, January 27, 2014 10:14 AM
Points: 1,322, Visits: 1,091
I'm going to go out on a short limb here and say: XML is an even worse idea than EAV. EAV Creates a weak data type design while XML creates a non-normalized weak data type design. You would never design a table that had a field Person that contained this: "FirstName: John; LastName: Doe; BirthDate: 1/1/1980"

So why would you want a field that contained " "

If you have to have customizable fields for searching or reporting purposes, fine, create an EAV table or two for that purpose. But don't design major parts of your database that way.
--
JimFive
Post #504001
« Prev Topic | Next Topic »

Add to briefcase «««123

Permissions Expand / Collapse