You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 9, 2023. It is now read-only.
Snaplet makes use of each column’s postgres type (e.g. text, int4) to determine how to parse it and serialize it, so that you can work with the value in your transform.ts file:
constconfig=()=>({public: {SomeTable: ({ row })=>({// If `name` is a `text` column, `row.name` is a stringname: copycat.firstName(row.name)})}})
This release fixes a bug, where we were looking up the column’s type incorrectly: if you had two tables of the same name (but appearing in different schemas), we would incorrectly always make use of the first matching table name we found (regardless of whether it was the actual matching table or not), and use its column types. We now will always make use of the actually matching table to determine which types to use for columns.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Snaplet makes use of each column’s postgres type (e.g.
text
,int4
) to determine how to parse it and serialize it, so that you can work with the value in yourtransform.ts
file:This release fixes a bug, where we were looking up the column’s type incorrectly: if you had two tables of the same name (but appearing in different schemas), we would incorrectly always make use of the first matching table name we found (regardless of whether it was the actual matching table or not), and use its column types. We now will always make use of the actually matching table to determine which types to use for columns.
Beta Was this translation helpful? Give feedback.
All reactions