.3.6 was stable (at least for me).

One of the issues to address is going to be the multi-DBAPI support. Keeping
all three stable at the same time can be tough. So starting .3.7, making
pyodbc the only supported configuration is OK with me, although I'll keep
pymssql up and running for the next couple of releases, as we're using it
here internally. Adodbapi is starting to look like a lost cause: emails are
going unanswered and there's been no updates for quite some time.

Speaking of testing, Paul has done a great job at bringing MSSQL up to speed
on a lot of the tests, and I believe there's only like four tests that don't
pass now, and I would wager those are because of database feature issues,
not overt bugs. Maybe it's time to start putting MSSQL on the regular test

On 4/26/07, Michael Bayer <[EMAIL PROTECTED]> wrote:
> On Apr 26, 2007, at 5:53 PM, Rick Morrison wrote:
> > Hey Mike, I think it may also be time to lift the "experimental"
> > label from the MS-SQL module, waddyasay?.
> yeah thats no prob, seems like only the current trunk has a stable
> version tho ?
> >
> > It may not be a 100% first-class SA citizen yet, but I think it's
> > damn close. If it will help with support, I'll donate a configured
> > VM with an installed version of MSSQL 2005 along with a real live
> > holographic whiz-bang M$ license and everything.
> of all the DB's it definitely gets the most external support.  I do
> have MSSQL 2005 running on a windows box here its just not in my
> normal course of testing procedures (largely because you guys are
> doing all the work testing anyway).
> >

You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 

Reply via email to