Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactor exception wrapping #855

Closed

Conversation

@aaugustin
Copy link
Member

aaugustin commented Feb 26, 2013

No description provided.

aaugustin added 6 commits Feb 26, 2013
It re-throws backend-specific exceptions using Django's common wrappers.
This covers the most common PEP-249 APIs:
- Connection APIs: close(), commit(), rollback(), cursor()
- Cursor APIs: callproc(), close(), execute(), executemany(),
  fetchone(), fetchmany(), fetchall(), nextset().

Fixed #19920.
This is now taken care of by the cursor wrapper.
Thanks Alex Gaynor for the proposal.
Thanks Jacob Kaplan-Moss for the suggestion.

The Django wrappers for database exceptions behave exactly the same as
the underlying database exceptions. See :pep:`249`, the Python Database API
Specification v2.0, for further information.

.. versionchanged:: 1.6
Previous version of Django only wrapped ``DatabaseError`` and

This comment has been minimized.

Copy link
@carljm

carljm Feb 27, 2013

Member

Previous versions (plural)

@aaugustin

This comment has been minimized.

Copy link
Member Author

aaugustin commented Feb 27, 2013

Merged.

@aaugustin aaugustin closed this Feb 27, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.