Feature 94 - Solution to Issue #94

[dash-]

Reworked ResultSet.getObjectIter() method. Generally refactored it, but also added logic to return null for integers rather than zero, which is detected via getObjectSync().

Also includes style fixes (tabs to spaces) for two files (lib/databasemetadata.js, lib/statement.js).

[dash-]

So this failed because two test runs had an ECONNRESET during the initial npm install. So it doesn't seem related to any of the changes. I'd like to tell travis.ci to "try again" but I'm not quite sure how yet.

[dash-]

Closed and re-opened to trigger Travis.ci rebuild.

[dash-]

Failed again due to network hangup (during npm install pre-step). On just one test this time (and a different test than the previous two). Between the two, all tests have passed. Closing and re-opening again to re-trigger travis.ci again.

[CraZySacX]

Looks like close open is the easiest way to restart the build on travis. You can also try git commit --allow-empty -m "Trigger" per http://stackoverflow.com/questions/17606874/trigger-a-travis-ci-rebuild-without-pushing-a-commit, but I haven't tested that.