Hi,
the example below demonstrates a bad side-effect of
sqlhub.doInTransaction(). I suppose the problem is, that
doInTransaction() restores the old connection unconditionally to
sqlhub.threadConnection, although self.getConnection() returns
sqlhub.processConnection in case it is set. And since
d
Oleg Broytmann phd.pp.ru> writes:
> > #3 is also intended to fix the "TypeError:unhashable instance using
> > sqlbuilder.Table" bug (SF#1642143) that was recently added
>
>Just yesterday I applied the patch
>
http://sourceforge.net/tracker/index.php?func=detail&aid=1673013&group_id=74338&atid
Hello!
On Wed, Mar 28, 2007 at 03:09:39PM +, Luke Opperman wrote:
> 1. SelectResults use SQLBuilder Select queries.
> 2. SQLBuilder Select supports rest of SelectResults options (reversed,
> distinct,
> etc)
> 3. SQLBuilder tablesUsedDict handles sqlrepr'able objects.
> 4. SQLBuilder Joins ha
After some time away, a chance to cleanup my changes to SelectResults and
SQLBuilder and submit them to all of you. Those changes fall into the following
areas:
1. SelectResults use SQLBuilder Select queries.
2. SQLBuilder Select supports rest of SelectResults options (reversed, distinct,
etc)
3.
