Carl Karsten wrote: > One thing I am totally in the dark in is how the server returns the number of > records processed by an UPDATE command.
Different servers can return this information, and if the Python connector can get that value back from the server, then it can report it in the return value from the cursor.execute() method. If so, then Dabo can get at it. > 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." It isn't. > What backend would prevent an UPDATE command from updating that would update > on > some other server? we are talking standard SQL UPDATE command, right ? I'd like to know, too. I could see a server knowing that client connection 1223 last queried the row prior to some other connection committing a change to it, and so when client 1223 goes to commit the server says "no way, you don't have the current data", but I don't know which server or servers would do this. > 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. The memento changes I'm working on could indeed lead to this, quite easily, if it is a real need. -- pkm ~ http://paulmcnett.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
