handle <null> type in query results #177
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
|
@madscientist I assume you will merge to master when you want to include it. |
Contributor
|
OK will do. |
madscientist
force-pushed
the
dbutson/null
branch
from
b9f36bb to
6b66753
Compare
Contributor
|
Pushed. You can delete the branch. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In order to support a type column being returned from engine. A TypeObject is needed instead of returning None. As None is used to verify that the type returned is in the TYPEMAP.
cursor.execute('select NULL from DUAL')
fails without this change. There are other cases where a user might explictly return NULL in place of an actual value. Say in a view such as INFORMATION_SCHEMA.COLUMNS where we don't support DOMAIN_NAME column.
The above example was added to tests/nuodb_types_test.py