I'm interested in the results too, as well as the ODBC config. I'm still in
the process of setting up a buildbot slave on Ubuntu that's going to be
running pyodbc as well. I normally use pymssql, and it'll be my first
serious go with pyodbc.
If it's OK with the list, maybe you can post the results right here, if not,
then please copy me on the attachments if you will.
Thanks,
Rick
On 6/6/07, Paul Johnston <[EMAIL PROTECTED]> wrote:
>
> Hi Ryan,
>
> To my knowledge you're the first to be using SA with pyODBC on Unix. For
> now you will have to edit the source code of mssql.py to change the DSN.
>
> Longer term, we will have to have a think about how to do this
> automatically. Perhaps we could look at the platform and if it's Windows use
> DRIVER={SQL Server} and otherwise use DRIVER={}.
>
> If you get a chance, I'd be very interested to see the output of the unit
> tests on Unix.
>
> Regards,
>
> Paul
>
>
>
> On 6/6/07, scurra <[EMAIL PROTECTED]> wrote:
> >
> >
> > Hi
> >
> > I cannot connect to SQL Server 2005 (Express) from my linux box using
> > the suggested SA method. I can connect to SQL Server using sqsh which
> > indicates that freetds and unixodbc are correctly set up.
> >
> > I can also connect using pyodbc. Although, only with the DSN method or
> > with DRIVER={}. For details, see:
> > http://sourceforge.net/forum/message.php?msg_id=4348161
> >
> > This is probably more of a pyodbc problem (or a problem created by me
> > (wouldn't be the first time)) so this post is more of an FYI and a
> > WTF? than a bug report ;-)
> >
> > The following thread contains reference to SA's pyodbc connection
> > mechanism:
> >
> > http://groups.google.co.uk/group/sqlalchemy/browse_thread/thread/b5909dceb2178a1d
> >
> > It seems that setting the DRIVER keyword to {SQL Server} is the method
> > employed by SA:
> >
> > def make_connect_string(self, keys):
> > connectors = ["Driver={SQL Server}"]
> > ...
> >
> >
> > So, I guess my questions are how I could get SA to use the DSN I have
> > defined in /etc/freetds/freetds.conf and /etc/odbc*.conf. Or, how I
> > could force SA to use DRIVER={} instead of Driver={SQL Server}. (Note
> > that, for me, the DRIVER keyword is case-sensitive when using pyodbc
> > directly.)
> >
> > Thanks for a kick-ass database doo-hicky (I am still getting to know
> > all the TLA's)
> >
> > Cheers,
> > Ryan
> >
> >
> >
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
