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

Hi, semi-lurker here, I'm using pyodbc, by the way. I had to comment out ``table.schema = queer`` before calling metadata.create_all() because MSSQL blows up: File c:\python24\lib\site-packages\sqlalchemy-0.4.5-py2.4.egg\sqlalchemy\data bases\mssql.py, line 499, in do_execute

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

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

[sqlalchemy] Re: SQLAlchemy experts wanted

On Fri, May 16, 2008 at 9:23 PM, Jim R. Wilson [EMAIL PROTECTED] wrote: Hi all, SQLAlchemy is a great project and a growing niche. As it becomes even more popular, there will be increasing demand for experts in the field. I am compiling a contact list of SQLAlchemy experts who may be

[sqlalchemy] Re: SQLAlchemy experts wanted

On Monday 19 May 2008 16:09:14 Gaetan de Menten wrote: On Fri, May 16, 2008 at 9:23 PM, Jim R. Wilson [EMAIL PROTECTED] wrote: Hi all, SQLAlchemy is a great project and a growing niche. As it becomes even more popular, there will be increasing demand for experts in the field. I

[sqlalchemy] update_or_insert

Hey, I'm using the SQL generation libs, and i'm wondering where the update_or_insert functionality is. I know at least mysql and sqlite have this functionality. I basically would like to be able to insert a new row without having to check if it exists first. Thanks David

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

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

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

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 message

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

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 ...

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

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

[sqlalchemy] Re: update_or_insert

you can use straight text or a text() construct to issue a mysql REPLACE statement, since only MySQL supports that operation. Theres also a recipe floating around somewhere which uses text() but automates the generation of the statement based on columns present, you might search on the

[sqlalchemy] Re: transactional sessions not transactional?

yes, this is kind of an unfortunate default that we've had throughout the 0.4 series, which we wont have in 0.5. To get the behavior you want, use this: engine = create_engine('postgres://...', pool_threadlocal=False) Alternatively, bind each session to the non-contextual connection,

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

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

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

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

[sqlalchemy] Re: Is inserting new data with column_mapped_collection inconsistent?

Allen Bierbaum wrote: On Fri, May 16, 2008 at 4:54 PM, jason kirtland [EMAIL PROTECTED] wrote: [..] Anyway, I think this is a bit non-intuitive. What I propose instead is that SA could automatically set the 'keyword' attribute of the Note object as part of the process of assigning it to the

[sqlalchemy] Custom caching

Hi, we have a DB app that uses SQLAlchemy and we'd like to add some custom DB caching logic. Unfortunately, there are no simple choke points that everything flows through where we could add this caching other than SQLAlchemy. We'd like to do things such as say invalidate the cache if tables X, Y

[sqlalchemy] Re: Custom caching

if youre looking to work at the statement interception level, we do have an API for that, called ProxyConnection, available in 0.5 under lib/sqlalchemy/interfaces.py. It seems like this would be required since you'd like to make decisions based on direct SQL execution. not sure how you'd

[sqlalchemy] Re: Custom caching

On May 19, 3:35 pm, Michael Bayer [EMAIL PROTECTED] wrote: if youre looking to work at the statement interception level, we do   have an API for that, called ProxyConnection, available in 0.5 under   lib/sqlalchemy/interfaces.py.  It seems like this would be required   since you'd like to

[sqlalchemy] Re: Custom caching

On May 19, 2008, at 3:40 PM, TP wrote: Yeah, can do it on top, but for various reasons I was hoping there was some sort of interface that would let me interpose code before inserts were executed and then I could grab the insert and queue it for later rather than have it execute now. Sounds

[sqlalchemy] SqlAlchemy and Stored Procedures with variables

Hi, We're trying to use SQLAlchemy with MS SQL Server 2000 using stored procedures. We connect to the server doing something like this: engine = sqlalchemy.create_engine('mssql:// user:[EMAIL PROTECTED]/db') cur = engine.connect() print cur.execute(execute stored_proc @query='gra%';).fetchall()

[sqlalchemy] Re: SqlAlchemy and Stored Procedures with variables

Does the same statement work in an interactive query window, complete with the embedded semicolon you're using? Also, you should be able to use positional parameters instead of named parameters in your call: cur.execute(execute stored_proc 'gra%' ) Note that as of yet there is no

[sqlalchemy] Re: SqlAlchemy and Stored Procedures with variables

On May 19, 2008, at 5:30 PM, Rick Morrison wrote: Does the same statement work in an interactive query window, complete with the embedded semicolon you're using? Also, you should be able to use positional parameters instead of named parameters in your call: cur.execute(execute

[sqlalchemy] (scoped_session.)commit() not doing anything

Hi, This commit()-not-doing-anything problem is driving me crazy :( All my other commits in the same code base are working perfectly, it's just this one. My Session is a scoped_session -- Session = scoped_session( sessionmaker(autoflush=True, transactional=True, ...)) A debug goes