For what it is worth I'm having the same new record failure issue on a table where the primary key is a varchar variable. Same trace data.
If I create a similar table but use an auto_increment integer for the primary key, new records can be inserted without error. On Nov 16, 2007 1:07 PM, Ed Leafe <[EMAIL PROTECTED]> wrote: > On Nov 16, 2007, at 9:49 AM, William Bryant wrote: > > > File "C:\Python25\lib\site-packages\dabo-0.8.1s-py2.5.egg\dabo\db > > \dCursorMixin.py", > > line 1037, in saverow > > self.__saverow(row) > > File "C:\Python25\lib\site-packages\dabo-0.8.1s-py2.5.egg\dabo\db > > \dCursorMixin.py", > > line 1150, in __saverow > > self.BackendObject.noResultsOnSave() > > Paul, something else isn't right. I realize that he's using a very > old version of dCursorMixin, but the line of code > 'self.BackendObject.noResultsOnSave()' can only be called for > existing records. Here's the code: > > newrec = self._newRecords.has_key(recKey) > [snip] > if newrec: > self._clearNewRecord(row=row, pkVal=recKey) > else: > if not res: > # Different backends may cause res to be None > # even if the save is successful. > self.BackendObject.noResultsOnSave() > > In other words, that line cannot be called on a new record. Either > the _newRecords dict isn't getting properly set, or it may have > something to do with new/empty record problem we ran into earlier. > > -- Ed Leafe > -- http://leafe.com > -- http://dabodev.com > > > > [excessive quoting removed by server] _______________________________________________ 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/dabo-users/[EMAIL PROTECTED]
