Type-parser configuration for every pg Pool the provider creates (pass as
types in pg.PoolConfig). node-postgres leaves NUMERIC/DECIMAL and BIGINT
text values as strings to avoid precision loss, but MemberJunction entity
metadata types those columns as number and all consumers (RunView results,
GraphQL serialization, Explorer UI) assume JS numbers — the contract the SQL
Server provider already delivers. Without this, UI code that does
cost.toFixed(4) throws and token totals string-concatenate instead of sum.
All other OIDs, and all binary-format values, use the pg defaults.
Type-parser configuration for every pg Pool the provider creates (pass as
typesin pg.PoolConfig). node-postgres leaves NUMERIC/DECIMAL and BIGINT text values as strings to avoid precision loss, but MemberJunction entity metadata types those columns asnumberand all consumers (RunView results, GraphQL serialization, Explorer UI) assume JS numbers — the contract the SQL Server provider already delivers. Without this, UI code that doescost.toFixed(4)throws and token totals string-concatenate instead of sum. All other OIDs, and all binary-format values, use the pg defaults.