Re: Inheritance...
Re: Inheritance...
- Subject: Re: Inheritance...
- From: Chuck Hill <email@hidden>
- Date: Wed, 7 May 2008 14:04:55 -0700
On May 7, 2008, at 1:37 PM, Guido Neitzer wrote:
On 07.05.2008, at 14:08, Mike Schrag wrote:
I would recommend AGAINST horizontal here -- You have 10 entities
in your hierarchy, which means 10 fetches every time you need to
fault an object of the root entity. I second Chuck on using single
table. Yes, your database is uglier, and you lose some of the
benefits of database not-null constraints, but this is really more
of an issue if other apps are using your database. For us, it's
almost never the case .. our WO apps get exclusive access to the
dbs generally, so as Chuck as said, the database is an
implementation detail. I let EOF worry about the fact that it has
a lot of columns.
Same here. I do only single table inheritance (for performance
reasons) and it always "just worked". Some of the apps had fairly
decent complexity and traffic.
I played around with the other inheritance styles but I always had
to worry about performance because buying decent hardware wasn't
that easy ... ;-)
And I normally don't have to worry about other technologies
accessing my databases.
I think that should be the deciding factor: if WO only then Single
Table is almost always the way to go. If you have to co-exist with
another technology or a legacy schema, them horizontal or vertical can
make your job easier at (usually) the expense of performance.
In either case, using inheritance is far, far better than hacking to
get around not using it.
Chuck
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden