diff options
| author | Dolph Mathews <dolph.mathews@gmail.com> | 2012-10-24 10:13:54 -0500 |
|---|---|---|
| committer | Dolph Mathews <dolph.mathews@gmail.com> | 2012-10-24 10:18:49 -0500 |
| commit | 5bb5e7a3503536c0439aa4e1948291648c2a0277 (patch) | |
| tree | 38b78419b0287ce0e49bc3e8408472c9b2a7837d /doc/source | |
| parent | 19224bddb30fa135c0cb0cedf8f0bd04103f3433 (diff) | |
Exception.message deprecated in py26 (bug 1070890)
In the case of IntegrityError (e), e is wrapping a DBAPIError[1] with more
information about the context of the exception -- context that we do NOT
want to expose to our own API users (however, that context should still
be logged). In the case of an integrity error, str(e.orig) will produce
exactly what we're producing with e.message today: a user-friendly
message such as 'column name is not unique'
This change should not impact what is logged or returned to the API
user -- just eliminate the deprecation warning.
[1]: http://docs.sqlalchemy.org/en/rel_0_7/core/exceptions.html#sqlalchemy.exc.DBAPIError
Change-Id: Ie3a5d93fbb5a7b90ad3b205bc8610f28b1626431
Diffstat (limited to 'doc/source')
0 files changed, 0 insertions, 0 deletions
