By moorage
via matthewpaulmoore.com
Published: Sep 17 2008 / 20:13
Using Memcached to Explore NoSQL
Neo4j App Performance Profile Management using New Relic
PyPy 1.8 Improves Performance, Maintains Business As Usual
JSR 356: Java API for WebSocket
Embedded Jetty, Vaadin and Weld
Increase Website Loading Speed With PHP Speedy
I’m a 17 year old developer up against a 19 year old, his company and a $1.1M investment | |
| HTML5 Canvas | |
| Written by: Simon Sarris | |
| Featured Refcardz: Top Refcardz: | |
| 150+ Refcardz Available · Get them all | |
By moorage
via matthewpaulmoore.com
Published: Sep 17 2008 / 20:13
Comments
onno.solin.eu replied ago:
"If you use STI, you will forever bind the two+ models together in ways that can be very hard to undo - a data migration is never fun."
I don't see what's wrong with building a class hierarchy using Single Table Inheritance. Sure the two+ models will be bound together: that's exactly the point, isn't it? The proposed alternative, using modules, is meant to cover another aspect of domain modeling altogether.
Either you talk about why inheritance is "wrong" (as opposed to using modules -- and they both have their use), or you talk about why STI is a bad implementation of inheritance. Simply stating that STI is a metric of "bad" code is outrageous.
Onno
,
,
Voters For This Link (16)
Voters Against This Link (0)