Re: Derived read-only attribute to expose PK [Was: Re: postgresql serial columns and wonder]
Re: Derived read-only attribute to expose PK [Was: Re: postgresql serial columns and wonder]
- Subject: Re: Derived read-only attribute to expose PK [Was: Re: postgresql serial columns and wonder]
- From: Paul Hoadley <email@hidden>
- Date: Thu, 04 Oct 2012 06:39:40 +0930
Hi Chuck,On 04/10/2012, at 1:53 AM, Chuck Hill wrote: Or just make it a class property. Some people find that offensive, but it won't cause problems for EOF. Exposed FK does cause problems.
I'm not one of those people, and I did consider that. What I've done instead is used the opportunity to look at ERXSequence and NativeDatabaseSequence in particular. This is one of those perennial "invoice number" situations, where all I really need is an increasing integer sequence. Integer primary key fit that bill, and I was happy to double up on it, but I'll probably use an additional native database sequence instead.
|
_______________________________________________
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