Hi Paul
Thanks for the advice. I have checked out the subversion SQLAlchemy,
made the change to mssql.py, and run the unit tests.
648c648
< connectors = ["Driver={SQL Server}"]
---
> connectors = ["DRIVER={}"]
src/sqlalchemy$ python test/alltests.py --dburi='mssql://
ryant:[EMAIL PROTECTED]/testdb' --verbose --coverage | tee -a sqlaut.log
Forgive my ignorance, but, would the .coverage file be enough or would
you need the log file as well. Where would you prefer I send any
attachments?
I'll gladly re-run the unit tests if need be.
Regards,
Ryan
On 6 Jun, 15:29, "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/b590...
>
> > 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
-~----------~----~----~----~------~----~------~--~---
