On 18/08/2011, at 11:05 PM, Kevin Hinkson wrote: > Since the best practice is to not make primary keys class properties, how do > I then create a qualifier that is based on the primary key of an EO?
My suggestion would be that you don't. Calling it a best practice isn't an arbitrary designation—there's an argument behind it. And if you buy that argument (whatever it is) for not making primary keys class properties, then the same argument applies to creating qualifiers based on the primary key. What does "not making a primary key a class property" mean if it doesn't mean "making the primary key inaccessible to the class"? So if you've got a business or technical case for exposing the primary key, just do it. It's only a best practice if you accept the argument behind it—maybe you have a genuine exception. -- Paul. http://logicsquad.net/ _______________________________________________ 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]
