Ed Leafe wrote: > On Dec 29, 2006, at 6:23 PM, Carl Karsten wrote: > >> I think there is a generic way of dealing with what John is talking >> about. I >> haven't seen anything like VFP's WhereType - did I miss it? > > No, because again, that's dependent on the backend. All that the > WHERE type buys you in VFP is the ability to detect such conflicts > ahead of time. If there is a conflict with a field that you are > updating and you select WHERE type of 1, Fox will merrily overwrite > the changed values. Some backends don't allow you to do that, due to > various locking schemes that deal with timestamps and such. Rather > than try to handle every possible conflict scenario for every > possible backend, I left it up to the developer to handle.
huh? someone is not understanding something. One thing I am totally in the dark in is how the server returns the number of records processed by an UPDATE command. VFP's conflict detection dosen't happen until after the SQL UPDATE command is processed by the server. so I don't see how that is "ahead of time." What backend would prevent an UPDATE command from updating that would update on some other server? we are talking standard SQL UPDATE command, right ? And it seems like the memento stuff you are working on to detect changes would be similar code to the "construct a where clause" that the various WhereTypes need. Carl > > -- Ed Leafe > -- http://leafe.com > -- http://dabodev.com > > > > _______________________________________________ > Post Messages to: [email protected] > Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev > > _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
