• 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: [JavaEOGenerator] Bug when generating fetchSpecification methods
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [JavaEOGenerator] Bug when generating fetchSpecification methods


  • Subject: Re: [JavaEOGenerator] Bug when generating fetchSpecification methods
  • From: "Mr. Pierre Frisch" <email@hidden>
  • Date: Fri, 21 Dec 2007 14:03:17 -0800

A class property is by definition visible, so if you have not marked it as visible no method returning a property will see it. An Attribute or a Relationship may be non-visible but an therefore not a property. EOEntity.anyRelationshipNamed or EOEntity.AnyAttribteNamed will return attributes and relationship that are not class properties.

Pierre
--
Pierre Frisch
email@hidden


On Dec 21, 2007, at 7:21, Oswaldo Bueno wrote:

Hi Art,
  Thanks for your reply.

  "Non visible attribute" -> An attribute(database column) included
in the eomodel, but not marked as a class property.

  I have already tested EOEntity._propertyForPath(), and it returns
null for attributes not marked as class property.

Cheers,
Bueno

On Dec 20, 2007 7:54 PM, Art Isbell <email@hidden> wrote:
On Dec 20, 2007, at 11:43 AM, Oswaldo Bueno wrote:

 I'm using JavaEOGenerator
<http://developer.apple.com/samplecode/JavaEOGenerator> to
auto-generate my entity classes.

 When it generates methods to access EOFetchSpecifications on the
eomodeld, it suppresses bindings associated with a non-visible
attribute.

What's a "non-visible attribute"? Do you mean a database column
that's not modeled in your eomodel? If so, why not include it in your
eomodel but don't make it a class property? That would prevent EOF
from including it in any SQL it generates. But I don't know whether
EOEntity._propertyForPath() would also ignore it. It would be quick
and easy to test.


Aloha,
Art

_______________________________________________
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

Attachment: smime.p7s
Description: S/MIME cryptographic signature

 _______________________________________________
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

References: 
 >[JavaEOGenerator] Bug when generating fetchSpecification methods (From: "Oswaldo Bueno" <email@hidden>)
 >Re: [JavaEOGenerator] Bug when generating fetchSpecification methods (From: Art Isbell <email@hidden>)
 >Re: [JavaEOGenerator] Bug when generating fetchSpecification methods (From: "Oswaldo Bueno" <email@hidden>)

  • Prev by Date: Re: Velocity EOGenerator+Eclipse+Wolips question
  • Next by Date: Re: 10.5 WO Migration, Add Host - Invalid Password - Access Denied
  • Previous by thread: Re: [JavaEOGenerator] Bug when generating fetchSpecification methods
  • Next by thread: WOLipps 3.3.1.1/3.3.4750 - Creating an embedded package...
  • Index(es):
    • Date
    • Thread