Ed Leafe wrote: > On Oct 30, 2006, at 4:12 PM, Paul McNett wrote: > >> However, there is obviously something wrong in either dBackend or >> dbFirebird that must just not ever get called normally. > > I don't think that's it. The line that initially triggered the > problem was the line that was trying to set the name of the table, so of > course running a SQL command before the table name is set will produce > the result Uwe reported.
Right. But recall that biz.setFieldVal() was being called from __setattr__, so it was being called for every single attribute setting operation on biz, so when the table name was being set, __setattr__ ran, setFieldVal() ran, and I had added code there to conditionally call dCursor.setFieldVal depending on whether or not the attribute was a field, and deciding whether or not the attribute was a field relied on DataStructure, which if not explicitly defined by the user/developer, ran getStructureDescription(), which it couldn't get yet because it didn't know the table yet. So... I think we are both right. I'm glad we've fixed the underlying problem (__setattr__/__getattr__). :) Paul _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
