Results 1 to 3 of 3
  1. #1
    Join Date
    Apr 2002
    Location
    Toronto, Canada
    Posts
    20,002

    Post-relational databases and Entity-Attribute-Value model

    COMMENTARY: Introduction to Dynamic Data Models in Healthcare

    tony, i thought you'd like to see that because of the EAV

    and was that really you who suggested this table:
    Code:
    person_name  item_type  item_name
    -----------  ---------  ---------
    eric         book       book1
    eric         book       book2
    eric         song       song2
    ...
    that looks an awful lot like an extensible "type/value" structure to me, eh

    rudy.ca | @rudydotca
    Buy my SitePoint book: Simply SQL

  2. #2
    Join Date
    Sep 2002
    Location
    UK
    Posts
    5,171
    Quote Originally Posted by r937
    that looks an awful lot like an extensible "type/value" structure to me, eh

    Yes, I did realise that even as I posted it! But I would argue that it is more of a supertype/subtype design that an EAV model really!

    I don't know what it is about the Healthcare and Pharmaceutical world that it seems to find EAV so beguiling. I mean, is it that they actually face a different situation from the rest of us where full-on flexibility is paramount, or is it just a culture thing - i.e. all the database designers in that industry pick up the EAV idea from each other like a, er, virus...?

  3. #3
    Join Date
    Feb 2004
    Location
    In front of the computer
    Posts
    15,579
    Quote Originally Posted by andrewst
    I don't know what it is about the Healthcare and Pharmaceutical world that it seems to find EAV so beguiling.
    It is the pharmaceuticals...

    This is sort of like LSD and BSD coming out of Berkeley. That is no accident either!

    -PatP

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •