On Jul 25, 2016, at 6:37 PM, Paul Hoadley <[email protected]> wrote: > > Hi Tim, > > On 26 Jul 2016, at 10:55 AM, T Worman <[email protected] > <mailto:[email protected]>> wrote: > >>> On Jul 25, 2016, at 6:03 PM, Theodore Petrosky <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>>> On Jul 25, 2016, at 6:03 PM, T Worman <[email protected] >>>> <mailto:[email protected]>> 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 protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
