Ed Leafe wrote: > On May 11, 2009, at 12:01 PM, Paul McNett wrote: > >>> Have you looked at the keys for this dict? Can you find a case where >>> a problem could actually occur? >> It's supposed to contain keys on a field name mapped to a value of a >> field type. It >> exists so we don't need to look it up each time. > > > No, that's not true. The key for this dict is defined: > > key = "%s:::%s" % (tableName, self.CurrentSQL) > > Look over dCursorMixin.getFields() first, and then let me know if you > have concerns.
Ok, I can see my concerns were unfounded. There would only be problems in true edge cases, such as someone having connections open to more than one database, those databases having tables of the same name, and those same-named tables having different structures. Paul _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/[email protected]
