-
Notifications
You must be signed in to change notification settings - Fork 45
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
field name or index with bad_result_process error #269
Comments
Hi Neel. Well, for the moment to get the field name it is possible to receive ozo::result (see result integration test for the details and then apply ozo::recv for a column value in a row to determine which one contains data type with an inappropriate OID. But with a composite type, unfortunately, there is no such mechanism to get rich debug information about the problem, since no stack-like context is provided for the deserialization functions. This situation is not convenient and should be improved for sure. So any help here is welcome. |
In a complected select query, An error message like the following makes it very hard to understand which field has a wrong type. And it takes time to find out the one which is wrong.
Is it possible to to have the field name or at least the field index attached with the error message ?
The text was updated successfully, but these errors were encountered: