Update documentation
Include minor version release notes Remove note about deprecation
This commit is contained in:
parent
ebc7969931
commit
3bfc8e9b68
4
NEWS.md
4
NEWS.md
@ -4,6 +4,10 @@ For richer information consult the commit log on github with referenced pull req
|
||||
|
||||
We do not include break-fix version release in this file.
|
||||
|
||||
### v1.1
|
||||
|
||||
- built in support for `JSON` data type for PostgreSQL Server @ v9.2.0 or greater
|
||||
|
||||
### v1.0
|
||||
|
||||
- remove deprecated functionality
|
||||
|
11
README.md
11
README.md
@ -82,17 +82,6 @@ The two share the same interface so __no other code changes should be required__
|
||||
* bulk import & export with `COPY TO/COPY FROM`
|
||||
* extensible js<->postgresql data-type coercion
|
||||
|
||||
## Heads Up!!
|
||||
|
||||
node-postgres is __very__ near to v1.0.0 release. Up until now I've tried to maintain all backwards compatilbity, but there are a few breaking changes the community has recommended I introduce.
|
||||
|
||||
The current version will spit out deprecation warnings when you use the soon-to-be-deprecated features. They're meant to be obtrusive and annoying. Understandable if you'd like to disable them.
|
||||
|
||||
You can do so like this: `pg.defaults.hideDeprecationWarnings = true;`
|
||||
|
||||
These are the breaking changes: https://github.com/brianc/node-postgres/pull/301
|
||||
|
||||
|
||||
## Documentation
|
||||
|
||||
Documentation is a work in progress primarily taking place on the github WIKI
|
||||
|
Loading…
Reference in New Issue
Block a user