• 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 problem...
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: inheritance problem...


  • Subject: Re: inheritance problem...
  • From: Tim Worman <email@hidden>
  • Date: Tue, 29 Dec 2009 18:46:28 -0800

OK, so, I've reviewed all the prototypes in use, data types, etc. I did find some areas where my prototypes were messed up so it was worth it to go through it all. The fk and pk both are long values.

But I'm still getting the same error. This solution also doesn't cross databases. It does crosses models at this point. But the TimeEntry and Timesheet entities are in the same model.

Tim Worman
UCLA GSE&IS


On Dec 28, 2009, at 4:45 PM, email@hidden wrote:

> Check cross database issues and also name sure the types on your pk and fk match ... I notice that says your fk is a long, make sure that matches the pk of the destination entity.
>
> Sent from my iPhone
>
> On Dec 28, 2009, at 7:33 PM, "Tim Worman"<email@hidden> wrote:
>
>> ...or wondering if I've modeled something incorrectly.
>>
>> I've got a model with these Entities:
>>
>> Timesheet (abstract parent)   >----------------- TimeEntry (just a time entry on a timesheet)
>> TimesheetExempt (child)
>> TimesheetNonExempt(child)
>>
>> Everything works fine until a given TimeEntry tries to refer back to its timesheet by calling timesheet(). At that point I get this error:
>>
>> Error:	java.lang.IllegalStateException: The object with globalID _EOIntegralKeyGlobalID[Timesheet (java.lang.Long)10253] could not be found in the database. This could be result of a referential integrity problem with the database. An empty fault could not be created because the object's class could not be determined (e.g. the GID is temporary or it is for an abstract entity)
>>
>> It is true that the GID would be for an abstract entity - Timesheet. But I assumed that a TimeEntry would not need to know specifically what variety of Timesheet it is dealing with. I guess the question I have is, what is the better way to model this? Will it be necessary for me to model TimeEntryExempt and TimeEntryNonExempt just so the time entries know which type of timesheet they belong to and don't call the abstract parent?
>>
>> Tim
>> UCLA GSE&IS
>>
>>
>>
>> _______________________________________________
>> 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

 _______________________________________________
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 problem...
      • From: David Avendasora <email@hidden>
References: 
 >inheritance problem... (From: Tim Worman <email@hidden>)
 >Re: inheritance problem... (From: email@hidden)

  • Prev by Date: Re: Wonder's ERPCategoryChart usage
  • Next by Date: Re: Refactor java files (Prev: OT: Refactor files into packages (Eclipse))
  • Previous by thread: Re: inheritance problem...
  • Next by thread: Re: inheritance problem...
  • Index(es):
    • Date
    • Thread