before I read the next 10 replies in this thread, this seems like an issue of too high of a transaction isolation level going on (something that plagued my SQL server apps when i was writing them, though that was years ago). cant the connection itself have a more lenient isolation level set ?
Arnar Birgisson wrote: > > Hi all, > > I'm using SA to build queries (no orm) and handle connection pooling > on a linux machine, connecting to mssql via freetds. > > This was working very well with SQL Server 2000, but a couple of weeks > ago we upgraded to 2005. Since then the SA app has been having some > problems. I've checked that I'm using the latest (0.64) version of > freetds - which was released to provide support for sql server 2005. > > Now, I won't go into the specific problems (mainly b/c I'm not sure > what's going on) but my dba suggested that I add "with (nolock)" after > each table alias in every query (I'm only doing selects). The problem > is that the queries are built and executed with SA. Can I plug into > some hooks or something to do this? > > Arnar > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
