On Jan 13, 2013, at 5:46 AM, Felix Schwarz wrote: > Am 12.01.2013 23:47, schrieb Michael Bayer: >> As I don't have the resources to maintain that text across changing MySQL >> versions, as well as the fact that the compatibility section is much more >> specific than what is present for any other dialect, > > Is that something were the community could help? For example if we had some > kind of test suite to run against different MySQL servers I could easily run > that regularly against MySQL 4.1, 5.0, 5.1 and 5.5.
We have a multi-backend suite established at jenkins.sqlalchemy.org though it is only against a single MySQL version. More MySQL versions to be tested against is not a bad thing, but the same problem exists probably moreso for Postgresql versions (early 8's through 9's) not to mention SQLite which has had many new features added and bugs fixed. But even beyond that, we also have to deal with the many DBAPI versions that exist for each of those backends. Overall, it's probably more critical to detect when particular bugs we've been working around are fixed, as opposed to detecting unsupported features. As far as the documentation section, I don't see what the listing of MySQL versions + features was documenting that is not already much better documented by MySQL's own documentation. I think it's better to have a simpler statement like "4.1 and forward works" - databases like these don't generally have any backwards incompatible changes and if they did, we'd document that explicitly. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected]. 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.
