Fallback to string for UUID columns #199
Open
+9
−3
Conversation
This file contains 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
|
Thanks for the PR @giorgiobasile would you able to provide a test case for this? 🙏 |
giorgiobasile
force-pushed
the
features_serialization_default
branch
from
89cc909 to
acbf1ad
Compare
|
Sure, just did! |
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.
Hi, I'm running into issues with UUID columns, basically being always returned as
nullin the OGC Features endpoints, whether they are recognized as featureidor be kept in the featureproperties.I pinpointed the issue to the default serialization function that handles only
Decimalserialization to string, and added another case forpgproto.UUID, but wondering if there is a better way to handle non-json-serializable fields. Hope it helps!