Re: Problems using primary key as attribute
Re: Problems using primary key as attribute
- Subject: Re: Problems using primary key as attribute
- From: Ricardo Strausz <email@hidden>
- Date: Mon, 18 Aug 2003 13:26:00 -0500
On sabado, agos 16, 2003, at 19:26 America/Mexico_City, Ray Ackland
wrote:
This is what I was hoping for, a simple solution. I had been
concentrating on doing it in code, rather than in EOModeler.
Only problem at this stage is I can't get it to work. As soon as I put
a derived attribute in EOModeler, the app goes funny not retrieving
the records (no SQL even generated).
I have tried it with a fresh project and EOModel, and trivial formula
(eg setting attribute to a fixed int) without success. I am using JVM
1.4.1, but using the settings to work around that. Will try it on
another machine tomorrow at work, which didn't have the 1.4.1 update
installed.
You can change your JVM to 1.3 in your targets (in PB).
Ray.
On Sunday, Aug 17, 2003, at 06:37 Pacific/Auckland,
email@hidden wrote:
Never tried but it should work. Use the client # as your primary key
but don't mark it as a class property and create a new read-only
attribute that maps to the primary key column.
HTH
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.