Support for unimplemented mappings

[uki00a]

Summary

When using types that are not implemented in decode.ts, the following error occurs:

Error: Don't know how to parse column type: <oid>

The following is a list of oids for which mapping is not yet supported:

• 22
• 27 (feat: Add tid and tid arrays support #228)
• 28
• 29
• 30
• 32
• 71
• 75
• 81
• 83
• 199 (Add json array and jsonb array type #179)
• 210
• 325
• 600 (Add support for point and point array type #185)
• 601 (feat: Add support for lseg and lseg array #233)
• 602 (feat: Add support for path and path array #235)
• 603 (feat: Support for box and box array #234)
• 604 (feat: Add support for polygon and polygon array #236)
• 628 (Add line decoder #232)
• 629 (Add line decoder #232)
• 702
• 703
• 704
• 705
• 718 (Add Circle type #237)
• 719 (Add Circle type #237)
• 790
• 791
• 1000 (Add bool and bytea array types #189)
• 1001 (Add bool and bytea array types #189)
• 1006
• 1008
• 1010 (feat: Add tid and tid arrays support #228)
• 1011
• 1012
• 1013
• 1016
• 1017 (Add support for point and point array type #185)
• 1018 (feat: Add support for lseg and lseg array #233)
• 1019 (feat: Add support for path and path array #235)
• 1020 (feat: Support for box and box array #234)
• 1021 (Refactor decoding #227)
• 1022 (Refactor decoding #227)
• 1023
• 1024
• 1025
• 1027 (feat: Add support for polygon and polygon array #236)
• 1028
• 1033
• 1034
• 1115 (Add support for timestamp #229)
• 1182 (feat: Add date array support #231)
• 1183
• 1185 (Add support for timestamp #229)
• 1186
• 1187
• 1231
• 1248
• 1263
• 1270
• 1560
• 1561
• 1562
• 1563
• 1790
• 2201
• 2249
• 2275
• 2276
• 2277
• 2279
• 2280
• 2281
• 2282
• 2283
• 2287
• 2776
• 2842
• 2843
• 2949
• 2970
• 3115
• 3220
• 3221
• 3310
• 3500
• 3614
• 3615
• 3642
• 3643
• 3644
• 3645
• 3807 (Add json array and jsonb array type #179)
• 3831
• 3838
• 3904
• 3905
• 3906
• 3907
• 3908
• 3909
• 3910
• 3911
• 3912
• 3913
• 3926
• 3927
• 4066

Please see 117#issuecomment-683205862 for details.

Related issues

• Don't know how to parse column type: 28 #117
• Don't know how to parse column type: 816425 #128
• Error: Don't know how to parse column type: 22 #178

[Soremwar]

After adding support for some of these types in the last days, I have decided that I will ship an "starter pack" of types that will have official support from the library. I have nearly completed that list, only lacking support for geometry types and date arrays.

After that list is completed, the default behavior of the app when it can't parse a result will be to return it as a string to the user, leaving up to them any possible transformation they want to make. From there, I will review possible data types to support officially on a case by case basis.

[Soremwar]

4376f4e just enabled string result as a default

[Soremwar]

Before 1.0, all types that must be parsed as something other than a string must be scratched from this list

[bombillazo]

We need to keep tracking these., We can use this as inspiration. Many of those oids are also highly specialized, not sure all need to be parsed, just the most used ones.