Hi Chuck, On 4 Dec 2015, at 4:15 am, Chuck Hill <[email protected]> wrote:
> I’d look at a less than generic solution in my thought experiment. Maybe > ERXEORepetition. And use some form of the global ID as the element ID for > the elements. Then in the implementation, you would do a map look up of the > global ID to get the EO, rather than an index lookup. I have not thought > this all the way through, but it seems doable. Each time in the reception > has a unique id (see uniqueKey on ERXWORepetition). There is no reason this > has to translate into an indexed lookup. That sounds good. I don’t know if I’ll go as far as building it, but that sounds like the kind of thing I was envisaging. On reflection, the “item not found”-type behaviour that we can already implement is probably sufficient. When the app gets to that point, it _knows_ the user’s data was stale when they made the selection. Retrieving the object somehow (if it still exists) and presenting it as though nothing went wrong probably isn’t the least surprising thing the app could do. -- Paul Hoadley http://logicsquad.net/
_______________________________________________ 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]
