• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Inheritance and relationships
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Inheritance and relationships


  • Subject: Re: Inheritance and relationships
  • From: Guido Neitzer <email@hidden>
  • Date: Fri, 8 Aug 2008 12:31:10 -0600

Update:

I have copied the affected models to a test app, deleted all other entities and all relationships and there it works fine. WTF???

More digging ...

cug



On 08.08.2008, at 12:15, Guido Neitzer wrote:

On 08.08.2008, at 11:11, Mike Schrag wrote:

* triple check that all your restricting qualifiers are set

Done. Seems all correct. That was my first thought.

* check that the restricting qualifier on your base class is set if it's not abstract

It was not set, but the entity is abstract. To make that clear what I'm dealing with (in that application, problem is everywhere the same):


Contact (abstract) -> Person -> BaseUser -> EventsUser

Restricting qualifier is set everywhere. I've just added it to Contact. But that one is abstract, so it doesn't matter.

* check that your restricting qualifier attributes are inherited in all the base classes (EM should not allow this NOT to be the case, but who knows)

Checked, and it's there.

* check that your restricting qualifier attributes are class properties

They are. Everywhere.

* are you using wonder's automatic restricting qualifier attribute settings? did you mean to have it on and you don't?

No. I have my ancient EVGenericRecord that does in init:

// set the inheritance type for entity inheritance
if (this.attributeKeys().containsObject("inheritanceType")) {
	this.takeValueForKey (entity().name(), "inheritanceType");
}

And right now, I'm only reading existing values from the database. No luck.

* double check that the type of your pk columns match the database -- that you're not mixing int and long here ... I think chuck ran into something crazy with this once.

contact_id is a "big int" from PostgreSQL and defined as a long in the model. That always worked for me.


* ..... profit?

Profit?

cug

--
http://www.event-s.net

_______________________________________________
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

-- http://www.event-s.net

_______________________________________________
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


  • Follow-Ups:
    • Re: Inheritance and relationships
      • From: Guido Neitzer <email@hidden>
    • Re: Inheritance and relationships
      • From: Chuck Hill <email@hidden>
References: 
 >Inheritance and relationships (From: Guido Neitzer <email@hidden>)
 >Re: Inheritance and relationships (From: Lachlan Deck <email@hidden>)
 >Re: Inheritance and relationships (From: Guido Neitzer <email@hidden>)
 >Re: Inheritance and relationships (From: Guido Neitzer <email@hidden>)
 >Re: Inheritance and relationships (From: Chuck Hill <email@hidden>)
 >Re: Inheritance and relationships (From: Guido Neitzer <email@hidden>)
 >Re: Inheritance and relationships (From: Chuck Hill <email@hidden>)
 >Re: Inheritance and relationships (From: Mike Schrag <email@hidden>)
 >Re: Inheritance and relationships (From: Mike Schrag <email@hidden>)
 >Re: Inheritance and relationships (From: Guido Neitzer <email@hidden>)

  • Prev by Date: Re: Inheritance and relationships
  • Next by Date: Re: Inheritance and relationships
  • Previous by thread: Re: Inheritance and relationships
  • Next by thread: Re: Inheritance and relationships
  • Index(es):
    • Date
    • Thread