Add many, many missing types to PostgresDataType #371
Merged
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.
IMPORTANT: This PR only deals with defining the well-known OIDs for Postgres built-in types. Except for adding more array/element type mappings, it does NOT add any additional support for any of these types, not even basic encoding and decoding! That support will be a separate PR.
Including but not limited to:
lseg
,path
,box
,polygon
,line
)reg*
types (regclass
,regtype
, etc.)macaddr8
,inet
,cidr
)bit
andbit varying
cstring
,internal
,any
,anycompatible
, etc.)tsvector
,tsquery
)numrange
,tsrange
,tstzrange
,daterange
)jsonpath
int4multirange
,nummultirange
, etc.)tid
,xid
,cid
,xid8
,pg_lsn
,trigger
, etc.)Also adds full two-way mappings for every known array type (including existing ones that were missing the mapping, like
money
).Requires minor version bump (adds new public API and deprecates
PostgresDataType.pgNodeTree
)