Fix database transport error

[ThePrez]

Database transport was throwing the following error:

getattr(cursor, self.func)(cursor, self.query, parms)
TypeError: callproc() takes at most 3 arguments (4 given)

This is because cursor is the implicit "self" reference but also being explicitly passed

[abmusse]

LGTM

[ThePrez]

All the TravisCI builds are failing, so we need to look into those.

[jkyeung]

Um, are we completely sure the tests are correct? Judging by the release downloads, the tests changed drastically between 1.5.1 and 1.6.0. Which isn't surprising, given the significant refactoring that was done.

But if anything, the tests should be failing on the 1.6.0 release, because this bug is a showstopper. Out of the box, DatabaseTransport is not usable at all from my PC (with the iSeries Access ODBC driver). But when I apply this fix, it works.

[Edit: I can confirm the bug prevents proper operation on PASE as well, using ibm_db.]

[ThePrez]

I agree. Opened issue #38 for the test case. Will merge this PR

[kadler]

Wow, I really goofed that up. Apparently when you reference Python methods, it doesn't return the underlying function, but a function bound to its self so you don't need to pass it.