Michael, if you're going to "correct" people in public, you really should try for a higher degree of accuracy.

Michael Bayer writes:

support for different databases is the responsibility of GNU Mailman,

Not so. First, "responsibility" is something we explicitly disclaim ("no warrantee", "as is", etc). Second, if code that works perfectly well with other MySQL-family databases fails with a specific product and version, we would be well within accepted practice to say "tough luck, use a compatible version". And third, SQLAlchemy advertises that it provides a common API independent of vendor and version of the backend database ... that's *why* we use it. Not to "avoid responsibility", but because the product does it very well. But it does mean we have almost no information about version quirks, and only very rarely do we see vendor-specific issues.

SQLAlchemy is a database access library that does not guarantee an application works with a particular database as it supports vendor-specific behaviors and constructs.

Sure, but we don't ask it to do anything vendor-specific, We use only APIs common to all RDBMSes we claim to support. To the extent that SQLAlchemy opts to use vendor-specific features to support those APIs, we don't know about it.

please dont mislead users into thinking the SQLAlchemy project is providing support for GNU Mailman,

I didn't. I said it *should* work, and if that's not good enough for the OP, I told them where to find people who would have data on their specific question.

thanks

You're welcome.

Steve