Custom types on the other side of the driver

[ABuffSeagull]

Since I've been using PostGIS a bit, I've wondered if there's a better way to deal with spatial data types.
Currently I just have:

export const geography = customType<{ data: never }>({
  dataType: () => "geography(Point,4326)",
});

This works pretty well, the never helping me catch when I'm trying to use it, since the data inside the DB is basically worthless once it's outside.
Unfortunately, the toDriver and fromDriver only work outside of the database, so there's nothing I can really do, and I have to do an ad hoc sql fragment every time:

sql<geojson.Point>`ST_Point(${table.column})::jsonb`

I wonder if there's a way you can template in some fragments every time the column is used directly in a select statement, like:

type LatLng = { lat: number; lng: number };
export const point = customType<{ inDB: LatLng; outDB: geojson.Point }>({
  dataType: () => "geography(Point,4326)",
  inDB: (arg: LatLng) => sql`ST_Point(${arg.lng}, ${arg.lat})`,
  outDB: (column: Column) => sql`ST_AsGeoJSON(${column})::jsonb`,
});

[Angelelz]

I think your inDB already exists in the form of toDriver and for outBD there is an open PR. In that PR it will be called customSelect.

[ABuffSeagull]

Wow, beating me to my own ideas? Love this library

[RowanAldean]

Can you explain where you're adding this fragment? I'm assuming somewhere in your actual db.select() call as part of the function chaining? As you've said, using the sql in the fromDriver doesn't work as it acts outside of the DB so can't use the PostGIS functions :'(