Update pg-promise to the latest version 🚀

[greenkeeper]

Version 6.1.0 of pg-promise just got published.

Dependency	pg-promise
Current Version	5.9.7
Type	dependency

The version 6.1.0 is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of pg-promise.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.

---

Commits

The new version differs by 2 commits.

• 4b1954d preparing the release.
• 1a56018 merging 6.x into master.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

[vitaly-t]

Looks like there will be some work required on your tests before version 6.x can be used.

The log is flooded with this error:

Connection pool of the database object has been destroyed.

which means that the test framework is calling pgp.end() at some point, to shut down the entire pg-promise library, and then later it continues making calls against the database, which is invalid.

It didn't come up against version 5.x of pg-promise because it was using a single global connection pool, and such granular fault detection wasn't possible.

[flovilmart]

Thanks for the tip! I’ll have a look!

[greenkeeper]

Version 6.1.1 just got published.

Update to this version instead 🚀

Commits

The new version differs by 2 commits.

• 14adfbb docs + upped the version.
• 44d501c Fixing #356, docs updates.

See the full diff

[vitaly-t]

There is some difference in 6.x for method pgp.end() now.

P.S. I wouldn't worry about upgrading now. The way pg-promise is used here, the upgrade to version 6.x won't offer any benefit.

[greenkeeper]

Version 6.1.2 just got published.

Update to this version instead 🚀

Commits

The new version differs by 4 commits.

• 068973d docs update.
• f996371 adding tests.
• d0a8a5e manually fixing eslint issue.
• b8e2127 adding ESLint rule for indents

See the full diff

[greenkeeper]

Version 6.2.0 just got published.

Update to this version instead 🚀

Commits

The new version differs by 8 commits.

• 32a70a9 docs.
• eceee51 code refactoring.
• 2980f20 fixing tests + travis.
• e679ac5 extending the task context.
• c8e1a4c docs.
• 7f4c4a1 docs.
• a73dfa2 docs.
• 18fee12 updating docs, following #359

See the full diff

[greenkeeper]

Version 6.2.1 just got published.

Update to this version instead 🚀

Commits

The new version differs by 5 commits.

• ed91f1e typescript update.
• 8061b74 adding task connected context flag
• e4c3292 typescript update.
• 5f81434 adding support for parent task context.
• 693dacc refactoring tasks.

See the full diff

[greenkeeper]

Version 6.2.2 just got published.

Update to this version instead 🚀

Commits

The new version differs by 3 commits.

• 71425a9 upped the version.
• c0b44ea adding event handler to direct connections.
• d145ff0 documentation updates.

See the full diff

[greenkeeper]

Version 6.2.3 just got published.

Update to this version instead 🚀

Commits

The new version differs by 5 commits.

• 665beef upped the version.
• ea54964 upped the version + dependencies.
• e5b2ba0 Merge pull request #363 from vitaly-t/error-test
• 631bc71 reverting custom errors to ES5
• aba2568 refactoring with eslint rule object-shorthand

See the full diff

[greenkeeper]

Version 6.3.0 just got published.

Update to this version instead 🚀

Commits

The new version differs by 9 commits.

• cf9a55d Merge pull request #364 from vitaly-t/direct-connections
• 229efb3 docs update.
• 66e4aca extending lost connection details.
• 355d7aa refactoring + documentation.
• cba92a4 extending the event.
• 4873af1 postpone removing the event listeners.
• a536ba5 connection error finished, it all works well.
• cf17714 adding lost to indirect connections.
• 7d9356f first draft for onConnectionLost

See the full diff

[flovilmart]

@vitaly-t I believe I got a fix, but this warning pops up:

WARNING: Creating a duplicate database object for the same connection.

can it be safely ignored? or should we change something in the createClient function?

[vitaly-t]

@flovilmart if it is in tests, it can be safely ignored. It just means that you keep creating copies of db with the same connection details, which the library considers an anti-pattern.

Alternatively, you can switch off all the warnings in tests, via Initialization option noWarnings.

[flovilmart]

That's all good not! Thanks for the guidance.

[vitaly-t]

That's all good not!

Pardon, you're saying it is no good? 😄

[flovilmart]

Haha, stupid typo! All good now, ran those on an isolated instance in the test suite. Way better