[IronPython] adodbapi 2.3.0 (the django version) released

[Ronnie Maor]

I was hoping for a "sure - this type of setup has been working for 6 months
now" :-)
Anyway, I'll try and play with it and report bugs.
thanks!

On Mon, May 3, 2010 at 11:35 PM, Vernon Cole <vernondcole at gmail.com> wrote:

> Not silly at all.  I just checked on their current documentation and
> adodbapi is still listed as an alternate engine for sqlalchemy for MS-SQL
> databases.  It is listed as at "development" level for Python 2.0. I
> communicated with the sqlalchemy team ages (3 years?) ago and asked what
> facilites they needed to have added. They requested a reliable .rowcount
> number. That has been done as of this release -- the change to using a
> client-side cursor by default should be the last step in making that work.
>
> In other words, you have picked the perfect time to work on this project.
>
> Please make sure to report any problems you find or tweaks you may need.
> This code will be in flux for a while -- I'm trying to get the little ends
> tied up before jumping in to true .NET support -- so get any requests in
> soon rather than late.
> --
> Vernon
>
> P.S.: I failed to thank JDHardy for patches to the alpha test version.
> Thanks!
> ---------------------------
>
>
> On Mon, May 3, 2010 at 1:25 PM, Ronnie Maor <ronnie.maor at gmail.com> wrote:
>
>> I'd like to play with sqlalchemy with IPy 2.6 (currently 2.6.0) and
>> talking to MS SQL database. will this package allow me to do this?
>>
>> (apologies if this is a silly question - I thought I'd save myself the
>> learning curve for understanding if it's silly or not...)
>>
>> thanks
>> Ronnie
>>
>> On Mon, May 3, 2010 at 12:37 PM, Vernon Cole <vernondcole at gmail.com>wrote:
>>
>>> Hello everyone.
>>>   I have just uploaded the latest version of adodbapi. This version is
>>> highly refactored following the work of Adam Vandenberg, and also has all of
>>> the current user suggested patches. Both the Mercurial tree and the
>>> downloadable zip files are updated.  (There is no fancy installer, just copy
>>> the folder in your site-packages folder.) This has been tested using CPython
>>> 2.3, CPython 2.6, IronPython 2.6 (.NET 2) and IronPython 2.6(.NET 4),
>>> accessing .mdb, MS-SQL and MySQL databases.  There is a separate .zip for
>>> Python 3.1.
>>> ............
>>> adodbapi
>>>
>>> A Python DB-API 2.0 module that makes it easy to use Microsoft ADO
>>> for connecting with databases and other data sources
>>> using either CPython or IronPython.
>>>
>>> Home page: <http://sourceforge.net/projects/adodbapi>
>>>
>>> Features:
>>> * 100% DB-API 2.0 compliant.
>>> * Includes pyunit testcases that describe how to use the module.
>>> * Fully implemented in Python.
>>> * Licensed under the LGPL license.
>>> * Supports eGenix mxDateTime, Python 2.3 datetime module and Python time
>>> module.
>>> * Supports multiple paramstyles: 'qmark' 'named' 'format'
>>> ............
>>> Whats new in version 2.3.0    # note: breaking changes and default
>>> changes!
>>>   This version is all about django support.  There are two targets:
>>>     A) MS SQL database connections for mainstream django.
>>>     B) running django on IronPython
>>>    Thanks to Adam Vandenberg for the django modifications.
>>>    The changes are:
>>>
>>> 1. the ado constants are moved into their own module: ado_consts
>>>       This may break some old code, but Adam did it on his version and I
>>> like the improvement in readability.
>>>       Also, you get better documentation of some results, like convertion
>>> of MS data type codes to strings:
>>>        >>> ado_consts.adTypeNames[202]
>>>        'adVarWChar'
>>>        >>> ado_consts.adTypeNames[cursr.description[0][1]]
>>>        'adWChar'
>>>   ** deprecation warning: access to these constants as adodbapi.ad* will
>>> be removed in the future **
>>>
>>> 2. will now default to client-side cursors. To get the old default, use
>>> something like:
>>>       adodbapi.adodbapi.defaultCursorLocation = ado_consts.adUseServer
>>>   ** change in default warning **
>>>
>>> 3. Added ability to change paramstyle on the connection or the cursor:
>>> (An extension to the db api)
>>>     Possible values for paramstyle are: 'qmark', 'named', 'format'. The
>>> default remains 'qmark'.
>>>     (SQL language in '%s' format or ':namedParameter' format will be
>>> converted to '?' internally.)
>>>     when 'named' format is used, the parameters must be in a dict, rather
>>> than a sequence.
>>>        >>>c = adodbapi.connect('someConnectionString',timeout=30)
>>>        >>>c.paramstyle = 'spam'
>>>            <<<will result in: adodbapi.NotSupportedError:
>>> paramstyle="spam" not in:('qmark', 'named', 'format')>>>
>>>   ** new extension feature **
>>>
>>> 4. Added abality to change the default paramstyle for adodbapi: (for
>>> django)
>>>     >>> import adodbapi as Database
>>>     >>> Database.paramstyle = 'format'
>>>  ** new extension feature **
>>>
>>> Whats new in version 2.2.7
>>> 1. Does not automagically change to mx.DateTime when mx package is
>>> installed. (This by popular demand.)
>>>    to get results in  mx.DateTime format, use:
>>>       adodbapi.adodbapi.dateconverter =
>>> adodbapi.adodbapi.mxDateTimeConverter
>>> 2. implements cursor.next()
>>>
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users at lists.ironpython.com
>>> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
>>>
>>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.ironpython.com
>> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
>>
>>
>
> _______________________________________________
> Users mailing list
> Users at lists.ironpython.com
> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ironpython-users/attachments/20100503/4da93520/attachment.html>