On Sep 24, 2008, at 2:43 PM, Paul McNett wrote:
> On one hand, so much of dCursor and dBizobj rely on the PK not
> changing.
> OTOH, we could probably hook into setFieldVal() so that, if it is
> the PK
> value changing, we can re-sync the _newRecords dict with the new pk
> value.
Of course, now you're adding lots and lots of unnecessary calls to
catch the rare instance where this happens.
There are several considerations to work through, mostly with
assumptions about how we mark a record as new. I was leaning toward a
system of storing all PKs from a requery(), and anything not in there
is a new record, but I didn't get time last night to work on it, as
several other things came up. I'm hoping to have time tonight to think
about it and maybe test out some ideas.
-- Ed Leafe
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message: http://leafe.com/archives/byMID/[EMAIL PROTECTED]
