Ed Leafe wrote: > On Dec 30, 2006, at 1:20 PM, Carl Karsten wrote: > >> What I am talking about is using a standard SQL UPDATE command, and >> then looking >> at how many records were updated (which may not be standard) to >> detect a >> collision. > > Python in general doesn't work that way. Normally, exceptions are > raised in response to failures, rather than some sort of return code. > dCursorMixin raises several types of exceptions, depending on the > situation: > > BeginningOfFileException > ConnectionLostException > DBNoAccessException > DBQueryException > EndOfFileException > FieldNotFoundException > NoRecordsException > QueryException > > You write your code to handle these exceptions, or else they > percolate back up to the UI, where they are displayed to the user by > default. >
Will NoRecordsException get raised if I do UPDATE foo SET Fid='a' WHERE 0=1 ? _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
