Never mind, I figured it out.
On Tuesday, July 9, 2013 1:07:29 PM UTC-4, Leonid Ilyevsky wrote:
>
> Thanks Michael, this solved the connection problem.
>
> Could you give me another tip? Now I am trying to get my Table()
> definition right, so the select statement will be a correct one.
> For mss
Thanks Michael, this solved the connection problem.
Could you give me another tip? Now I am trying to get my Table() definition
right, so the select statement will be a correct one.
For mssql, it must be something like:
select a, b, c from mydb.dbo.mytable
I just tried to play with it, and I sp
On Jul 9, 2013, at 11:18 AM, Leonid Ilyevsky wrote:
> I have exact same problem. Any good news on this?
> How come it works fine with just pyodbc but not with sqlalchemy? Looks like
> alchemy does not pass all parameters down properly.
this issue has been resolved, if you must use Python 3 wit
I have exact same problem. Any good news on this?
How come it works fine with just pyodbc but not with sqlalchemy? Looks like
alchemy does not pass all parameters down properly.
On Thursday, March 7, 2013 1:58:23 PM UTC-5, Michael Bayer wrote:
>
> its Python 3 related. that particular ticket ref
its Python 3 related. that particular ticket refers to how bad of an
experience I have when trying to get pyodbc to run well on OSX especially in
Python 3. if things have improved, I can try working on it at least in a Linux
VM (I still have low hopes for OSX).
On Mar 7, 2013, at 1:41 PM, Da
Hi,
when I try to connect with sqlalchemy and mssql+pyodbc I get this exeption:
"TypeError: The first argument to execute must be a string or unicode
query".
It works if I only use pyodbc.
E.g.
>>> conn = pyodbc.connect('DRIVER={SQL
Server};Server=127.0.0.1;Database=BOM;UID=guest;PWD=guest')
>
