[Enhancement] Add support for additonal types which are created via extensions e.g Geospatial objects. #139
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.
This request is in accordance to #130 (comment). After doing some searching, types created by
CREATE EXTENSION extension_name
are dynamic and are not static unlike datatypes fully supported by postgres. The only way to get their type_id and typeString is to query the pg_types table in postgres.This will enable people to extend the library easily once they have a way of decoding and encoding the data types from dart objects to pg_type as well as from the types in postgres to dart objects.
This change will enable adding extra types from
to
If PR is accepted, support for geospatial objects using extension https://postgis.net and queries is already using this feature is implemented with some tests on this branch https://github.com/bettdouglas/postgresql-dart/tree/geospatial-support which closes
stablekernel/aqueduct#747
stablekernel/aqueduct#634
#120
The query_reuse_test.dart is failing though. I may need help fixing that.