On Aug 18, 2007, at 1:01 PM, Paul Johnston wrote:
> > Hi, > > I have just started using SA 0.4 in anger. Getting on ok, I'm starting > to like the new query syntax as I get used to it. I've do have some > problems though... > > 1) MSSQL queries on tables with schemas are broken; I get queries > like this: > UPDATE tsr.sequences SET nextval=? WHERE sequences_1.seq = ? > Now, I've got a workaround for now, which is to disable the automatic > aliasign for schema tables, but we will need to figure out a proper > fix. OK. keep in mind we have a mssql.py dialect test suite now, where if possible you can put SQL compilation tests against the generated strings themselves, so that the tests run on a non-MSSQL test run. > > 2) Using ActiveMapper causes a bunch of deprecation warnings. > I'm going to have a look at updating ActiveMapper to use > scoped_session. > Any objections to this? Or anything I should watch for? You can make whatever changes needed to ActiveMapper, but keep in mind the whole extension itself is deprecated ;) (of course it will be around for awhile since turbogears depends on it) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
