added NextResultSet implementation

[kmpm]

Trying to revive the solution for issue #380

Shamelessly used the stuff that @basvanbeek created in pr #453 but added some testing with postgres.
This would also work with mssql but I didn't want to mess with the test environment.

[kmpm]

@jmoiron, what is the preferred way of getting something like this included?

[BenKnigge]

This project appears to have been abandoned I've merged this into my own fork here https://github.com/BenKnigge/sqly
If anyone else would be interested in going through this pr black log and merging them into my fork the help would be welcomed.

[tazimmerman]

This project appears to have been abandoned I've merged this into my own fork here https://github.com/BenKnigge/sqly If anyone else would be interested in going through this pr black log and merging them into my fork the help would be welcomed.

@BenKnigge Should we use your fork or https://github.com/go-sqlx/sqlx? I recall seeing your name link to that fork as well in another issue or PR comment.

[kmpm]

@dlsniper, what kind of testing do you have in mind?
I have used it with sqlserver alot, but I don't know how much work it would be to add it to the test environment.

[dlsniper]

Hi @kmpm I've tagged this as needs testing because it's something that would benefit having the automated CI tests in place before merging. I plan to integrate that in the extremely near future and then I think it will be good to go. I'll take a closer look at it in the next couple of weeks or so, there are plenty PRs to get to and this is more complex than some of the other ones.

Thank you for being so patient about it and for your contribution.

[kmpm]

The most complex thing with this PR is actually the test. The funtional part of the code is actually quite straight forward .

[kmpm]

Hi @DSniper, what kind of tests are you missing.
Preferably there should be some tests for mssql but that is not one of the database engines in the default test environment for this project.