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 PROTECTED]> 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 protected]) > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/webobjects-dev/bueno.dev%40gmail.com > > This email sent to [EMAIL PROTECTED] > _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
