On Sep 5, 2008, at 10:16 AM, Paul McNett wrote:
> 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.
Why is this considered 'short-circuited'? I would interpret setting
the bizobj's SQL property to mean that they want to explicitly set the
SQL, and not use the AutoSQL.
> 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.
Yeah, I've been really busy. I try to stay on top of questions, but
don't have the time to switch from Rackspace coding to Dabo coding
most days.
setWhereClause() never even touches the bizobj - it's a simple pass-
through to the cursor. Nothing that you are reverting changes this. I
believe that your initial hunch that somewhere he is running biz.SQL =
<something> is the culprit. John, can you please grep your code to see
if this is indeed the cause of your problem? That's the only thing
that could have been affected by the change to biz.SQL.
-- Ed Leafe
_______________________________________________
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]
