On 7/6/06, Chris Perkins <[EMAIL PROTECTED]> wrote:
The MS-SQL database module is still rather young and green, but it should be getting some TLC over the coming weeks. It has been updated to the 0.2 API, but it has been only lightly tested -- Right now its author tests and uses it only for SQL operations, not with the mapping API. Updates are planned, but until then patches are welcome, as always.
This is most likely a problem with the test suite more than the database module. Different databases support various features at various levels, and the test suite likely assumes too much. AFAIK, Mike is planning on an install of MS-SQL on his machine soon, and can then hopefully adjust the test suite to accommodate the module. This, coupled with the aforementioned TLC, should make the MS-SQL module a first-class citizen soon enough.
Rick
Two questions:
1) Are there differing levels of support for different databases?
Specifically, should I expect mssql to work properly in 2.4? I
understand that the mssql module was contributed, but I don't know if
it has kept up with the API changes in the 2.0 series. Do you test
all the supported databases, or only a specific subset of them, before
releasing an X.Y version?
The MS-SQL database module is still rather young and green, but it should be getting some TLC over the coming weeks. It has been updated to the 0.2 API, but it has been only lightly tested -- Right now its author tests and uses it only for SQL operations, not with the mapping API. Updates are planned, but until then patches are welcome, as always.
2) Running the unittests - I follow the directions in
README.unittests, but the result is:
Ran 302 tests in 4.828s
FAILED (failures=11, errors=147)
I assume that this is not the expected result. I am on Windows XP,
using 1684 from svn.
It appears to pass (most of) the first 50 or so tests, then starts to
fail/error nearly all of them, starting at orm.mapper.EagerTest.
However, if I run only the orm.mapper.EagerTest, it passes. Any idea
what's going on? Should all of the tests pass?
This is most likely a problem with the test suite more than the database module. Different databases support various features at various levels, and the test suite likely assumes too much. AFAIK, Mike is planning on an install of MS-SQL on his machine soon, and can then hopefully adjust the test suite to accommodate the module. This, coupled with the aforementioned TLC, should make the MS-SQL module a first-class citizen soon enough.
Rick
Chris Perkins
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Sqlalchemy-users mailing list
Sqlalchemy-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ Sqlalchemy-users mailing list Sqlalchemy-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
