Re: updateSome() has difficulty with WHERE arguments

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Okay, I understand what's going on now. Sorry I wasn't able to 
understand that before (I'm a little slow sometimes).

On a related note, I did notice one additional change that was made (I 
believe to handle a sequence of strings for the init argument of 
initAlias). I think you meant something like this:

Index: src/pydo/dbi.py
===================================================================
- --- src/pydo/dbi.py     (revision 1636)
+++ src/pydo/dbi.py     (working copy)
@@ -248,6 +248,7 @@

      """
      if isinstance(init, basestring):
+        sql=init
          def init(conn):
              c=conn.cursor()
              c.execute(sql)

Without the additional sql=init statement, a connection to the database 
will fail if the init argument to initAlias was a single string (i.e., 
c.execute(sql) will fail because sql was not set at the time the inner 
init func was defined).

	-- Matt


On Aug 19, 2005, at 05:11, Jacob Smullyan wrote:

> On Thu, Aug 18, 2005 at 10:15:29PM -0700, Matthew Bogosian wrote:
>>
>> I will be the first to admit that I have no idea what kind of voodoo
>> magic goes on in the updateSome method, but I have noticed a behavior
>> that seems to be erroneous.
>
> Yes, it certainly is (was!).
>
> ...

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (Darwin)

iD8DBQFDBecMnLpDzL5I7l8RAqMiAJ9ox/cMBAduvxTV6vo7ao9Ai5kRmgCfXeQa
H3PDw1dgdoE8LR+vf9/WPRQ=
=p71n
-----END PGP SIGNATURE-----



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf