Wow, sweet!

That is going to be a *huge* addition. Let me know when you're close enough
to do some MSSQL testing.

Rick

On Jan 17, 2008 4:35 PM, jason kirtland <[EMAIL PROTECTED]> wrote:

>
> Rick Morrison wrote:
> > Adodbapi is Windows-only, you're definitely barking up the wrong tree
> > with that one.
> >
> > Pyodbc on Linux is theoretically possible, but I know of no users and
> > have very little experience myself with it.
> > Pymssql is supported on Linux, and it works within certain restrictions
> > (30 char identifier length, no unicode) as outlined on the SQLAlchemy
> wiki.
> >
> > You're pretty much breaking new ground if you're trying pyodbc +
> > SQLAlchemy + Unix. Not that I'm discouraging that, I've been meaning to
> > tackle it, but just so you know....
> >
> > But Linux + adodbapi is not going to fly at all.
>
> A devel aside: I have pyodbc on Unix nearly working with MySQL.  I
> haven't tried pyodbc/MSSQL from Unix yet.
>
> I've got a local branch going to formalize the multi-driver support &
> ease using SQLAlchemy on alternate VMs.  Adding ODBC to a single-driver
> dialect in CPython was my step 1, next up is sqlite via JDBC for Jython,
> and then the same in IronPython.
>
> -J
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
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 
http://groups.google.com/group/sqlalchemy?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to