Comment 1 for bug 1346662

Revision history for this message
Ben Nemec (bnemec) wrote :

I'm going to untag this as low-hanging-fruit because there is some historical context here that was lost in the move to filter decorators. The important thing to note is that for SQLAlchemy exceptions e.message != str(e), so this can't just be fixed the easy way most of the other cases of this problem were. We need to fix the problem, and then verify that all of our regexes on all of the supported engines still work.

See the original comment warning about this here: http://git.openstack.org/cgit/openstack/oslo-incubator/tree/openstack/common/db/sqlalchemy/session.py#n373