Re: wrong column name with eo and relationships
Re: wrong column name with eo and relationships
- Subject: Re: wrong column name with eo and relationships
- From: John Larson <email@hidden>
- Date: Wed, 19 Jul 2006 07:05:23 -0500
I am so ashamed.
Since I was changing so many objects at once I made a check list to
walk through to make sure that I caught as many things as I could.
Apparently I forgot one.
Though I used the createsubclass menu item to minimize the risk of
typos, forgotten relationships, etc. I didn't pay attention to the
fact that EOModeler defaults subclasses to abstract when it makes the
subclass. So, I didn't have "Uncheck abstract in subclass inspector"
on my list. This morning, while picking through a subclass plist
file, I saw it staring right at me.
When I was in college (where we had a whole network of NeXT
computers ;-) ) I played around with OS/2. I remember
troubleshooting fmy brand-spanking new Canon BJ-600 color printer -
state of the art - or over a day. So state of the art that I had to
gopher to find drivers for it. I troubleshooted and troubleshooted
and in the end it was that the printer wasn't plugged in. Now I am
older (and apparently as dumb), but I share that story with my
employees to stress the need for peer consultation to prevent the "it
must be the driver!" or in this case "it must be eomodeler!"
judgments that invariably lead you further from the problem than to it.
So, thank you to those who helped me fix my eomodeler. It was really
stupid.
John
On Jul 18, 2006, at 11:58 PM, John Larson wrote:
I checked and double checked. I tried leaving the abstract table's
name blank and marking it as read only because that's what the
example did in the horizontal example with the abstract objects.
Same thing.
When I did this change, I made 8 entities abstract and created 23
subclasses. Not one relationship from any entity to any one of the
8 abstract classes works. I'm going to bed, but the only thing I
could see that looked odd was the internalInfo / _nameInObjectStore
entry. For each subclass, the nameInObjectStore was set to the
abstract class's Java class name. I tried deleting it, renaming
it, and basically making a mess before I needed sleep.
I've done this before and its worked! This is ridiculous! The
fact that not one of the entities works makes me think that it has
to be something more fundamental from when I made the objects
abstract. I have included the plist file for an abstract entity
and a subclass. (they're the smallest ones i have)
_______________________________________________
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