Rick Morrison escreveu:
> So now I'm of two minds about which module to use and if I should use
> a schema or not for these porposes.
There's a few arcane limitations when using the pymssql module, pyodbc
will be better-supported going into the future. As for using schema vs.
other namespace tri
> So now I'm of two minds about which module to use and if I should use
> a schema or not for these porposes.
There's a few arcane limitations when using the pymssql module, pyodbc will
be better-supported going into the future.
As for using schema vs. other namespace tricks, that's up to you. I w
Hi,
So now I'm of two minds about which module to use and if I should use a
> schema or not for these porposes.
I'm using PyODBC and schemas, and things work just fine for me. Ok, some
error messages aren't quite there, but it works well enough for me.
Paul
--~--~-~--~~
Paul Johnston escreveu:
This isn't an SQLAlchemy or DBAPI issue - you just need to create the
schema with the correct permissions.
True; I've already solved the problem, after I got this (much better)
error message by using pymssql. The first traceback:
* happened in a "SET IDENTITY ..." in
Hi,
The specified schema name "queer" either does not exist or you do not have
> permi
> ssion to use it.
This isn't an SQLAlchemy or DBAPI issue - you just need to create the schema
with the correct permissions.
Paul
--~--~-~--~~~---~--~~
You received this mess
Rick Morrison wrote:
I won't have a chance to look at this under pyodbc until tomorrow. In
the meantime, if you could try with pymssql to see if you get the same
error, that will help in debugging this.
What is the recommended module to use on win32? Yes, pymssql does help:
I had to create the
That error would be thrown by an insert, not a table create, and I believe
there are other users using pyodbc with schema-specified tables without
problems.
I won't have a chance to look at this under pyodbc until tomorrow. In the
meantime, if you could try with pymssql to see if you get the same
