brianc 6f8292435d Respond to emptyQuery with a sync message ...

When a __prepared statement__ has no body in the query the backend responds with an `emptyQuery` message but never with a `commandComplete` or `errorResponse` message.  The client was hanging forever waiting for one of the other two expected messages.  The server was hanging forever waiting for the client to respond with a `sync` message.  This change has the client send the required `sync` on receipt of an `emptyQuery` message when the query is a prepared statement.  Fixes #822

2015-08-01 18:51:49 -05:00

..

native

Add warning for native bindings

2015-06-07 10:20:48 -04:00

client.js

Respond to emptyQuery with a sync message

2015-08-01 18:51:49 -05:00

connection-parameters.js

switch to pg-connection-string module for parsing

2014-07-06 16:39:22 -07:00

connection.js

Add warning on long query names

2015-05-21 13:17:04 -04:00

defaults.js

Break type parsing into separate module

2014-03-15 15:36:27 -05:00

index.js

Make native bindings an optional install

2014-10-18 00:20:18 -04:00

pool.js

Only call destroy on a client when it is not already being destroyed

2014-07-30 14:17:04 +02:00

query.js

Respond to emptyQuery with a sync message

2015-08-01 18:51:49 -05:00

result.js

Implemented per-client type parser overrides.

2014-12-03 10:38:57 -06:00

type-overrides.js

Moved type override code into a new class.

2014-12-03 11:00:27 -06:00

utils.js

Removed various unused vars

2014-04-09 08:46:17 -04:00