mx.ODBC 2.0.7 bug?

[Joe]

Hi Steve,

Thanks, I find you get much better help when you provide the details needed 
for your case instead of expecting others to invest alot of their time 
before you did your homework.

Thanks for sending it over to Marc.  Last time I found a bug in the mx stuff 
(YEARS AGO) I sent it directly to Marc but was trying not to bother him 
until I tried the list first.

One point I forgot to mention in the previous reply is that AFTER the 
converter function is setup and used if you examine the 
cursor.description[column][1] values it still has the old sqltype and 
sqllen.  Not sure if that would be considered a bug or not?  I would have 
expected that the converter hook would have also modified the description 
info to match what the converter hook did.

Thanks again for your assistance.

Regards,

Joe


> This is a very nice piece of deduction, and I am copying this message to 
> you and to the egenix-users list, since that's generally a reliable way to 
> get Marc-Andre's attention.
>
> I'm not convinced that it demonstrates an mxODBC bug, since I don't 
> believe that the ampersand is actioned by the drivers, but I'm not the 
> best one to be authoritative about this.
>
> others-who-read-this-reply-will-ly y'rs  - steve
> -- 
> Meet the Python developers and your c.l.py favorites March 23-25
> Come to PyCon DC 2005                      http://www.pycon.org/
> Steve Holden                           http://www.holdenweb.com/