Re: PyDO's policy on handling LOBs?

On Wed, Jun 29, 2005 at 12:24:49PM +0100, [email protected] wrote:
> For LOBs both cx_Oracle and DCOracle2 (and maybe other DB-API
> modules) return objects that provide a 'read' method. Is there a
> policy on how a PyDO database driver is expected to deal with such
> objects - just pass them on for the client code to read, or read
> them first and pass on the content?

No, there hasn't been, but I think you did the right thing in the
oracle driver.  If people don't want the hit associated with the LOB
for a query, they can use a projection and eliminate it, and use
another query to get it as needed.

I don't know if the use of cursor.next() is going to have performance
implications for that driver; if it does, perhaps a different approach
should be taken when there are no LOBs.  But I guess you can't
easily determine that in advance. 

Unfortunately, I don't have any machine that is a candidate for
groaning under the weight of Oracle, so I can't test or fiddle at the
moment.  

Cheers,

js

-- 
Jacob Smullyan

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFCwrZZuqamFyFXXLIRAg4MAJ9Poh6GnKt5xGfsJg+Ws3IznMTM3ACg0Hb1
U1uV2mkeNcNW4ixLRHXMTSY=
=rKVc
-----END PGP SIGNATURE-----