Improve error message accuracy of native SendQuery

* add private method const char *GetLastError() to src/binding.cc
* add var const char *lastErrorMessage to SendQuery in src/binding.cc
* throw result of PQErrorMessage inside SendQuery

This commit replaces the static/vague error message "PQsendQuery
returned error code" with the actual message text of the error.
The method GetLastError() returns the text of PQErrorMessage.
GetLastError is called from within SendQuery to retrieve the message.
remove unnecessary whitespace
Fix for issue #165. Use libuv events instead of libev events.
Change return type of Cancel() to bool.

This should fix the following warning on windows:

..\src\binding.cc(117): warning C4800: 'int' : forcing value to bool 'true' or
'false' (performance warning)

Spotted in issue #165.
Add conditions to the binding.gyp for windows, linux, mac.
Change library extension for windows build.

Thanks to image72!
Update README.md

Added Vendly to production use section
Merge pull request #197 from andresgottlieb/patch-1

Update README.md
Merge pull request #196 from booo/uv_events

windows build
ignore hanging tests
version bump
Export types module
add test for exported types
Merge remote-tracking branch 'kongleaks/improveSendQueryErrorMsgAccuracy' into pull/188
version bump
Use JS Date's getFullYear() in first example.

In year 2012, seeing the output of 112 confused me, and would potentially
confuse any JS noob. I thought it was some bug in node-postgres.

Presumably, JS starts counting time from Jan 1, 1900!

Also, according to [1], getYear() is deprecated and one should use getFullYear()
instead.

[1] http://www.w3schools.com/jsref/jsref_obj_date.asp
enable IPv6 support when using native bindings
Merge pull request #213 from gurjeet/use_getFullYearInExample

Use JS Date's getFullYear() in first example.
Merge pull request #215 from natesilva/ipv6-native-support

enable IPv6 support when using native bindings
make 1st example not hang in readme