[IronPython] Fwd: adodbapi 2.2.1 (bugfix) release.
vernondcole at gmail.com
Sun Sep 7 16:23:19 CEST 2008
[My attempt to send this to two mailing lists at once seems to have failed.
This is a retry. -- VC]
I found a bug in adodbapi v2.2 already. When putting data into a numeric
database column, if the input was in a string (as for example the value of a
wxPython grid cell), then the data would be truncated to the binary length
of the field. So if I tried tried putting "12345" into an integer column,
the value 1234 would be stored, because integers are 4 bytes long. This took
me a while to find, since I kept looking at my wxwidgets code before finally
uncovering adodbapi as the culpret.
The fixed version is in the pywin32 CVS and in
For some good news, Mike Driscoll reports:
I used your adodbapi module in my wxPython / SqlAlchemy program today and it
> seemed to be returning the same data as the default module (which I think is
> pyobdc). I don't know if my application truly stresses adodbapi , but it
> does make lots of calls and accesses multiple tables in multiple databases.
If anyone can test SqlAlchemy -> adodbapi -> IronPython please let us know
if it works.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ironpython-users