On Sunday 31 December 2006 06:08, Paul McNett wrote: > Carl Karsten wrote: > > Much like I want the database engine to make sure I don't create orphan > > child records, I want some low level generic code that makes sure > > database updates don't get overridden. I doubt I am the only one. > > I agree with you, Carl, that Dabo should provide some basic behavior for > detecting and responding to collisions. Then, the application developer > can decide to override, circumvent, or expand on the basic behavior Dabo > provides. > > Adding the list of fields to the where clause seems like a pretty smart, > generic way to accomplish this. VFP got a lot of things right, and this > is one of them. I don't see why it wouldn't work with all backends, and > anyway the app developer can set it to not detect but overwrite updates > if they choose.
Let be get this right. If I have a 100 field table and I want to change one field the update statement will look something like this: Update table set myfield = "something" where 99 fields = 99 fields??? This will insure that the fields I didn't change were not changed? Do I have it right? -- John Fabiani _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
