thanks for the reply -
Rick Morrision wrote:
Perhaps Sarge includes the Sybase TDS libraries in the distro.
it does, but the version in sarge doesn't seem to have some functions in
it called by _mssql.so:
import pymssql
Traceback (most recent call last):
File "<stdin>", line 1, in ?
File "/usr/lib/python2.4/site-packages/pymssql.py", line 24, in ?
import _mssql
ImportError: /usr/lib/python2.4/site-packages/_mssql.so: undefined
symbol: dbcolinfo
IMO, the cleanest way to go is to build FreeTDS from source and use
pymssql against that.
i did this:
- removed debian-sarge's libsybdb
- built freetds-0.63 from source, which put libsybdb.so.5 in /usr/local/lib
- put /usr/local/lib in /etc/ld.so.conf and ran ldconfig
...but _mssql still tries to use /usr/lib/libsybdb.so.3, according to:
ldd /usr/lib/python2.4/site-packages/_mssql.so
i was able to get pymssql to apparently work by symlinking:
ln -s /usr/local/lib/libsybdb.so.5 /usr/lib/libsybdb.so.3
however, i don't know how robust this is, and wonder if there is a less
hacky way.
my apologies if this isn't directly sqlalchemy-related. fortunately or
unfortunately, debian's package system has met most of my needs in the
past and i haven't done much installation from source. i'd really like
to use python with our mssql server at work, and this has roadblocked me.
thanks again for any suggestions
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Sqlalchemy-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
