+ 1

I only discovered the relationship wizard a few weeks back and it resulted in EOModeler finally being retired from our development tool kit. We are 100% Entity Modeler now. The only area i think Entity Modeler is still weaker than EOModeler is for building fetch specifications, but it's definitely usable in it's current state.

I'm now trying to eliminate WOBuilder from by brain. That's a tougher call, but having discovered and fallen in love with inline bindings (wonder style) i'm getting there...

Simon

On 14 Jan 2008, at 17:20, Mike Schrag wrote:

You are only one key stroke away from disaster.
That, and with the relationship wizard in Entity Modeler, other than if you are using a reverse-engineered model where the entities already contain keys, it should be MUCH faster. The relationship wizard will do one-to-many, many-to-one, many-to-many, flattened or not, create foreign keys for you automatically, wire everything up, etc. If you're not using it, you should, because (IMO) it's the #1 productivity enhancement in Entity Modeler. It takes a tedious ~4-5 step process and makes it one.

ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [EMAIL PROTECTED]

Reply via email to