Update connection-parameters.js

The current connection url handling fails when the password contains
encoded special characters: After the encodeURI, the special
characters from the password are double encoded, and the password is
rejected by postgres.

Proposed fix handles one level of double encoding, and while it
might break compatibility with passwords like "asdfg%77fgh" (which
would've been escaped to asdfg%2577fgh before this patch), I
strongly feel that maintaining backwards compatibility is in this
case less important than following standards and discouraging bad
coding practices.
Update connection-parameters.js

Different double-encode removal strategy
Update creation-tests.js

added unittest for urlencoded components
Merge pull request #1 from za-creature/master

unittest
Update creation-tests.js

connection exports 'database' instead of 'path'
Update connection-parameters.js
remove reference to pool when destroying

Leaving a reference to the pool means the
destroyed pool will get returned if you
later try to reconnect with the same
connection string.
big integer array support
parse values in float arrays as floats not strings

javascript numbers are 64-bit floating numbers
test array/int2
test array/int4
test array/int8
test array/float4
test array/float8
Parse date type as local time
initial changelog
Merge branch 'pull/326'

Conflicts:
	lib/connection-parameters.js
	test/unit/connection-parameters/creation-tests.js
Merge pull request #395 from aaronyo/master

Unable to reconnect after calling pg.end()
Merge pull request #501 from lalitkapoor/GH-452

improve support for int arrays and float arrays
Merge pull request #514 from benighted/parse-date-as-local

Parse date type as local time