Skip to content
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

Add custom serialization for some PostGIS types. #7757

Merged
merged 1 commit into from
Sep 16, 2024

Conversation

vpetrovykh
Copy link
Member

Scalars box2d and box3d need custom serialization for a binary protocol because they don't have one provided by PostGIS. However, they can be serialized as geometry instead because there are casts between both of these types and geometry that preserve all relevant information.

@vpetrovykh vpetrovykh force-pushed the postgis_serialization branch from 5f80b13 to 7e82107 Compare September 16, 2024 18:43
Scalars `box2d` and `box3d` need custom serialization for a binary
protocol because they don't have one provided by PostGIS. However, they
can be serialized as `geometry` instead because there are casts between
both of these types and geometry that preserve all relevant information.
@vpetrovykh vpetrovykh force-pushed the postgis_serialization branch from 7e82107 to 65911a1 Compare September 16, 2024 19:07
@vpetrovykh vpetrovykh merged commit 625214a into master Sep 16, 2024
23 checks passed
@vpetrovykh vpetrovykh deleted the postgis_serialization branch September 16, 2024 19:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants