From b8412273eaa625d55faf1b29b0cb237f0a7230f7 Mon Sep 17 00:00:00 2001 From: Charmander <~@charmander.me> Date: Fri, 1 Jun 2018 00:26:25 +0000 Subject: [PATCH] pg-pool now throws an error when calling done === client.release multiple times --- FAQ.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/FAQ.md b/FAQ.md index bf55931..35691e3 100644 --- a/FAQ.md +++ b/FAQ.md @@ -192,9 +192,7 @@ It will wait, and call your callback with a connection after one becomes availab ### 18. (New Question) Is there a way to check if I have an active connection? -### 19. (New Question) Do I correctly assume that calling done() or done(err) more than once (multiple times) has no side-effects? - -### 20. I obtain `Promise { }` from a query +### 19. I obtain `Promise { }` from a query See https://github.com/brianc/node-postgres/issues/1130. The query returns a promise because of its asynchronous design. You should use a callback, the `then` method or await. Callback example: