The 0.3.7 bug is my fault, I checked in the changes without testing on pyodbc. Didn't know that Mike would cut 0.3.7 the very next day! Guess I'll get to use that buildslave for something after all...
Paul, I wasn't aware of scope_identity() not working on pyodbc, I checked it in because it was your patch and I know you work on pyodbc. It worked OK here with pymssql, so I let it go. Can you detail what the problem is with pyodbc? In the meantime, I'll make the @@IDENTITY version the default again until it's straightened out. Rick On 5/1/07, Paul Johnston <[EMAIL PROTECTED]> wrote: > > > Hi, > > I've found SA/MSSQL is mostly stable now. I do have a few bugs > outstanding, and I'm sure I'll need to dive into the source code again > in the future, but it's comparably stable to the rest of SA. > > The unit test failures are right down, at least on Windows. I haven't > tested PyODBC on other platforms; we should do that ASAP (at least as a > one off exercise). I'm definitely in favor of a buildbot although I > can't easily offer hardware. > > Anyway, I'm sure you're dying to hear the outstanding problems! Well, in > my usual form of totally undecipherable notes for self, here they are: > > #538 - identity insert problems > label subqueries in from clause - unit test proposed in #513 triggers this > new unit test - len(unistr) == db.func.length(unistr) > date formatting - pass as datetime objects not strings > make MSNVarchar derive from Unicode > #537 - scope_identity(). This always returns NULL on PyODBC ticket open > on PyODBC tracker > > BTW, I'm a bit worried that 0.3.7 has a bug that means fetch IDs doesn't > work (except with PyMSSQL), but I haven't checked this. Hopefully we'll > get these little issues fixed, then from 0.3.8 SA will always ship with > all unit tests passing for MSSQL. Woo! :-) > > Paul > > > Rick Morrison wrote: > > > .3.6 was stable (at least for me). > > > > One of the issues to address is going to be the multi-DBAPI support. > > Keeping all three stable at the same time can be tough. So starting > > .3.7, making pyodbc the only supported configuration is OK with me, > > although I'll keep pymssql up and running for the next couple of > > releases, as we're using it here internally. Adodbapi is starting to > > look like a lost cause: emails are going unanswered and there's been > > no updates for quite some time. > > > > Speaking of testing, Paul has done a great job at bringing MSSQL up to > > speed on a lot of the tests, and I believe there's only like four > > tests that don't pass now, and I would wager those are because of > > database feature issues, not overt bugs. Maybe it's time to start > > putting MSSQL on the regular test rotation. > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
