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
Overriding default handling to, say, parse numeric types, is a common thing to want to do, but in the call types.setTypeParser(20, function(val) { return parseInt(val, 10)}) taken from the readme, how are types identified? 20 represents what? Without this information, I'm helpless?
The text was updated successfully, but these errors were encountered:
The built-in types that come with PostgreSQL have well defined "low" values. Custom types created by end users have higher values and may change across servers as the exact value depends on the order of creation.
There is much that should be improved with this readme:
Tone (informal -> professional)
Sections (background vs. example)
Links (to PostgreSQL documentation)
PRs welcome and if I have some time I'll rewrite it myself. But ultimately the readme is pretty clear that these are OIDs and provides you with SQL commands to see the full set, which will tell you the corresponding number for every type in your database.
Overriding default handling to, say, parse numeric types, is a common thing to want to do, but in the call
types.setTypeParser(20, function(val) { return parseInt(val, 10)})
taken from the readme, how are types identified? 20 represents what? Without this information, I'm helpless?The text was updated successfully, but these errors were encountered: