Re: ERXGenericRecord and UUID's
Re: ERXGenericRecord and UUID's
- Subject: Re: ERXGenericRecord and UUID's
- From: Paul Hoadley <email@hidden>
- Date: Tue, 26 Jul 2016 12:35:12 +0930
Hi Tim,
On 26 Jul 2016, at 11:34 AM, T Worman <email@hidden> wrote:
If you’ve observed a change that you haven’t opted in for, then it could be a bug. Could you describe it all more fully, and open a GitHub issue?
Issue #1 was addressed by a subsequent patch which checks for a null prototypeName() on the primary key attribute(s).
Ah, OK—so, to be completely clear, there’s no longer anything you’d describe as “not opt-in”? (Although we occasionally nominate points where we’ll forego backwards compatibility for a good reason, such as Wonder 7, I think it’s super-important to make the “principle of least astonishment” our default position.) But...
Issue #2 I could use some feedback. I would not have experienced the bug at all if prototypeName() wasn’t returning null even though the attribute in question has a prototype designated.
You think there still might be a bug.
I am sure Samuel will be able to take a look.
|
_______________________________________________
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