Code

Changes between Version 32 and Version 33 of ModelInheritance


Ignore:
Timestamp:
05/05/06 15:36:20 (8 years ago)
Author:
anonymous
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ModelInheritance

    v32 v33  
    7777''-Joseph Kocherhans'' 
    7878 
     79''Thanks Joseph.  Agree it's not an obvious choice.  The Null thing is important, although wonder whether it's more important than performant queries... a bit philosophical that one: is it better to ensure cleaner data in the db or provide more performant code.  It could be dealt with using triggers, but I know that then gets away from declarative constraints into procedural programming in the DBs.  Aside from the different syntax, not all DBs even support triggers (sqlite?). 
     80 
     81Stepping back, it's possible (likely) there will be situations where one or the other is preferred.  It should be possible to allow for that by abstracting the approach into a Strategy (per Strategy pattern).  Even though there's only one strategy provided initially, it would allow the (an-) other to be added later.  Wonder if that's something you're considering? 
     82 
     83 - S 
     84'' 
    7985 
    8086=== 2. Modeling joins in SQL ===