johnf wrote: > On Wednesday 03 September 2008 04:10:58 pm Paul McNett wrote: >> johnf wrote: >>> Looks like the dBizobj is using SQL and not UserSQL. Also it may be >>> related to the problem I'm having at the moment where I can't seem to add >>> a where clause using self.PrimaryBizobj.setWhereClause() >>> >>> /home/johnf/downloads/dabo/dabo/biz/dBizobj.py:2006: DeprecationWarning: >>> This property is deprecated, and will be removed in the next version >>> of the framework. Use the 'UserSQL' property instead. >>> of the framework. Use the 'UserSQL' property instead."""), >>> DeprecationWarning, 1) >> If you go back to dabo [4497] does your setWhereClause() problem go away? > >> There is something potentially wrong. Could be that the old code used to >> do: >> >> self.SQL = self.getSQL() >> >> which would use the output from the sql-builder methods, where UserSQL >> was intended for user code to completely override the sql builder stuff. >> So this change may have made it impossible to use the sql builder. >> >> However, my apps seem to work fine, so I could very well be misreading >> the changeset or missing something. >> > using "svn up -r 4497" fixes the issue with setWhereClause. Just in case you > were wondering.
Yeah, the issue boils down to crossed connections between: biz.setSQL() biz.getSQL() biz.UserSQL biz.AutoSQL biz.SQL, AFAICT, was never meant to be a property to set, but merely a property for getSQL()/setSQL() to use. But now that SQL just sets UserSQL, the AutoSQL gets short-circuited. Unfortunately, I don't have time to dig into this right now, and Ed's been fairly quiet which makes me think he doesn't have much time either, so I'll revert most of the change, leaving a DeprecationWarning in place. Paul _______________________________________________ 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/[EMAIL PROTECTED]
