All major and minor releases are briefly explained below.
For richer information consult the commit log on github with referenced pull requests.
We do not include break-fix version release in this file.
- Use single row mode in native bindings when available [@rpedela]
- reduces memory consumption when handling row values in 'row' event
- Automatically bind buffer type parameters as binary [@eugeneware]
- Respect PGSSLMODE environment variable
- Ability to opt-in to int8 parsing via
pg.defaults.parseInt8 = true
- Use eval in the result set parser to increase performance
- Remove built-in support for binary Int64 parsing. Due to the low usage & required compiled dependency this will be pushed into a 3rd party add-on
- Add support for SSL connections in JavaScript driver
- this means you can connect to heroku postgres from your local machine without the native bindings!
- Add field metadata to result object
- Add ability for rows to be returned as arrays instead of objects
- Properly handle various PostgreSQL to JavaScript type conversions to avoid data loss:
PostgreSQL | [email protected] JavaScript | [email protected] JavaScript
--------------------------------|----------------
float4 | number (float) | string
float8 | number (float) | string
int8 | string | number (int)
numeric | string | number (float)
decimal | string | number (float)
For more information see brianc#353 If you are unhappy with these changes you can always override the built in type parsing fairly easily.
- Make client_encoding configurable and optional
- return field metadata on result object: access via result.fields[i].name/dataTypeID
- built in support for
JSON
data type for PostgreSQL Server @ v9.2.0 or greater
- remove deprecated functionality
- Callback function passed to
pg.connect
now requires 3 arguments - Client#pauseDrain() / Client#resumeDrain removed
- numeric, decimal, and float data types no longer parsed into float before being returned. Will be returned from query results as
String
- Callback function passed to
- client now emits
end
when disconnected from back-end server - if client is disconnected in the middle of a query, query receives an error
- add deprecation warnings in prep for v1.0
- fix read/write failures in native module under node v0.9.x