#2 Error handling

[Pavel Gubin]

1. It would be fine to have access to numeric error code
(Connection::_errno) without subclassing Connection class. For
example, if Query::fetch() returns anything but OCI_NO_DATA one
can prefer to propagate the error. Logging facility is not sufficient
here because program can not see precise result of the operation.

2. Is Orapp suitable for use in multithreaded environment? I.e. can
I create Connections in several threads? If so why Connection::
_errno is static? This way one can miss error while creating new
Connection in different thread.

Thanks,
Pavel