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 18:36:42 -0700
On Jul 25, 2016, at 6:23 PM, Paul Hoadley < email@hidden> wrote:
On 26 Jul 2016, at 10:47 AM, T Worman < email@hidden> wrote:
On Jul 25, 2016, at 4:13 PM, Paul Hoadley <email@hidden> wrote:
Hi Tim,
On 26 Jul 2016, at 7:33 AM, T Worman <email@hidden> wrote:
1. The new (and very cool) UUID stuff in ERXGenericRecord is NOT opt-in. :-)
Could you explain this observation a bit further?
Sorry, that was just me being sarcastic about what we all do and that new behaviors (even good ones) happen sometimes regardless of whether we choose them or not.
Yeah, I understood the sentiment, I just want to know more about what you’ve observed. Any new behaviour should very definitely be opt-in, and as Ted noted, I would have thought that it was. If it’s not, let’s work through it. -- Paul Hoadley http://logicsquad.net/
The class variable _primaryKeyDictionary gets lazily instantiated in ERXGenericRecord.rawPrimaryKeyDictionary.
ERXGenericRecord.rawPrimaryKeyDictionary(boolean inTransaction) now calls ERXGenericRecord.createUuidPrimaryKey any time inTransaction is <true> and _primaryKeyDictionary is null. Previously, inTransaction was only evaluated if _primaryKeyDictionary referenced cached primary keys. Nothing happened otherwise.
I was somewhat assuming that the 2nd issue I encountered was maybe the cause of the situation - the fact that attributeName() was returning null on my primary key attribute. I do want to figure out what is happening there.
Tim |
_______________________________________________
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