[sqlalchemy] Re: MSSQL dislikes schema= on table.create()

[Luis Bruno]

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 schema (wtfrak was I thinking...) Meanwhile, the stack trace isn't corrupted when using pymssql:

---8<---

ne\base.py", line 942, in _handle_dbapi_exception

validated=is_disconnect)

message 2760, severity 16, state 1, line 2:

ssion to use it.
---8<---


mssql://:@host/db

File "c:\python24\lib\site-packages\sqlalchemy-0.4.5-py2.4.egg\sqlalchemy\engi raise exceptions.DBAPIError.instance(statement, parameters, e, connection_in sqlalchemy.exceptions.DatabaseError: (DatabaseError) internal error: SQL Server The specified schema name "queer" either does not exist or you do not have permi Side note: I wish easy_install pymssql*.exe would have put ntwdblib.dll inside the .egg directory; that was a false start. Also, pymssql+SA doesn't support SSPI authentication using the syntax presented earlier:

Luis Bruno wrote:

File

bases\mssql.py", line 499, in do_execute
    cursor.execute("SET IDENTITY_INSERT %s OFF" %
self.identifier_preparer.format_table(context.compiled.statement.table))

"c:\python24\lib\site-packages\sqlalchemy-0.4.5-py2.4.egg\sqlalchemy\data SystemError: 'finally' pops bad exception

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.

It happens on metadata.create_all(). Also, I've verified that "finally pops bad exception" happens on other exceptions, like failure to connect (this using pyodbc).

signature.asc
Description: OpenPGP digital signature