# 🔍 Description This is the follow-up of #5686, renaming `./pyhive` to `./python`, and also adding `**/python/*` to RAT exclusion list temporarily. "PyHive" may not be a suitable name after being part of Apache Kyuubi, let's use a generic dir name `python`, and discuss the official name later(we probably keep the code at `./python` eventually). ## Types of changes 🔖 - [ ] Bugfix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) ## Test Plan 🧪 Recover RAT checked. --- # Checklist 📝 - [x] This patch was not authored or co-authored using [Generative Tooling](https://www.apache.org/legal/generative-tooling.html) **Be nice. Be informative.** Closes #6279 from pan3793/pyhive-1. Closes #5686 42d338e71 [Cheng Pan] [KYUUBI #5686][FOLLOWUP] Rename pyhive to python Authored-by: Cheng Pan <chengpan@apache.org> Signed-off-by: Cheng Pan <chengpan@apache.org>
73 lines
2.1 KiB
Python
73 lines
2.1 KiB
Python
"""
|
|
Package private common utilities. Do not use directly.
|
|
"""
|
|
from __future__ import absolute_import
|
|
from __future__ import unicode_literals
|
|
|
|
__all__ = [
|
|
'Error', 'Warning', 'InterfaceError', 'DatabaseError', 'InternalError', 'OperationalError',
|
|
'ProgrammingError', 'DataError', 'NotSupportedError',
|
|
]
|
|
|
|
|
|
class Error(Exception):
|
|
"""Exception that is the base class of all other error exceptions.
|
|
|
|
You can use this to catch all errors with one single except statement.
|
|
"""
|
|
pass
|
|
|
|
|
|
class Warning(Exception):
|
|
"""Exception raised for important warnings like data truncations while inserting, etc."""
|
|
pass
|
|
|
|
|
|
class InterfaceError(Error):
|
|
"""Exception raised for errors that are related to the database interface rather than the
|
|
database itself.
|
|
"""
|
|
pass
|
|
|
|
|
|
class DatabaseError(Error):
|
|
"""Exception raised for errors that are related to the database."""
|
|
pass
|
|
|
|
|
|
class InternalError(DatabaseError):
|
|
"""Exception raised when the database encounters an internal error, e.g. the cursor is not valid
|
|
anymore, the transaction is out of sync, etc."""
|
|
pass
|
|
|
|
|
|
class OperationalError(DatabaseError):
|
|
"""Exception raised for errors that are related to the database's operation and not necessarily
|
|
under the control of the programmer, e.g. an unexpected disconnect occurs, the data source name
|
|
is not found, a transaction could not be processed, a memory allocation error occurred during
|
|
processing, etc.
|
|
"""
|
|
pass
|
|
|
|
|
|
class ProgrammingError(DatabaseError):
|
|
"""Exception raised for programming errors, e.g. table not found or already exists, syntax error
|
|
in the SQL statement, wrong number of parameters specified, etc.
|
|
"""
|
|
pass
|
|
|
|
|
|
class DataError(DatabaseError):
|
|
"""Exception raised for errors that are due to problems with the processed data like division by
|
|
zero, numeric value out of range, etc.
|
|
"""
|
|
pass
|
|
|
|
|
|
class NotSupportedError(DatabaseError):
|
|
"""Exception raised in case a method or database API was used which is not supported by the
|
|
database, e.g. requesting a ``.rollback()`` on a connection that does not support transaction or
|
|
has transactions turned off.
|
|
"""
|
|
pass
|