Michael Bayer zzzcomputing.com> writes:
> On Apr 22, 2013, at 12:44 PM, Dan Lenski gmail.com> wrote:
>
> > I get your point about not crufting up DBAPI with a bunch of high-level
> > features that will need to be reimplemented for each module...
> >
> > But
Michael Bayer zzzcomputing.com> writes:
> On Apr 21, 2013, at 9:39 PM, Daniel Lenski gmail.com> wrote:
>
> >
> > I *could* pass around a handle to the DB module along with the cursor
> > itself, as you've suggested, but that seems redundant and error-prone
> > to me. To my mind, this is a sma
Vernon D. Cole gmail.com> writes:
> Dan:
> You have a very good point. Perhaps we should put that on the wish list for
API version 3.
> The .connection attribute of the cursor is optional. IMHO it should be
required.. I think most existing api packages implement it.
> The it is suggested, b
On Fri, Apr 19, 2013 at 11:46 AM, Michael Bayer
wrote:
>
> On Apr 19, 2013, at 1:56 PM, Dan Lenski wrote:
>
>> The problem I'm having is... how can I figure out what are the
appropriate
>> type objects for this comparison if I *only* have access to the cursor
o
lass__.__module__] #FIXME!
if cur.description[0][1] == mod.STRING:
print "first column is STRING data type"
Is there a more robust and elegant solution to this? It seems like there
ought to be a module-independent way to introspect the column data types in
the
