Re: ERXGenericRecord and UUID's
Re: ERXGenericRecord and UUID's
- Subject: Re: ERXGenericRecord and UUID's
- From: T Worman <email@hidden>
- Date: Mon, 25 Jul 2016 19:04:07 -0700
On Jul 25, 2016, at 6:37 PM, Paul Hoadley <email@hidden> wrote:
Hi Tim,
On Jul 25, 2016, at 6:03 PM, Theodore Petrosky < email@hidden> wrote:
1. The new (and very cool) UUID stuff in ERXGenericRecord is NOT opt-in. :-)
I also don’t understand “is NOT opt-in”. To use this, I have to change the prototype of the id column from id to uuid.
Of course the migration has to be fixed by hand from: personTable.newBlobColumn("id", NOT_NULL); to personTable.newUuidColumn("id", NOT_NULL);
Theodore,
In my case, the new code runs regardless of how my model is set up. It runs anytime the primary keys are not cached and “in transaction” is <true>. With the old behavior nothing happened if “in transaction” was <true> (with the exception of simply returning the cached keys or null if not cached).
The javadoc API hasn’t changed at all.
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).
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.
Any ideas?
|
_______________________________________________
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