Fixes #316 : set return null for HydratingResultSet::current() on no data

[samsonasik]

Provide a narrative description of what you are trying to accomplish:

• Are you fixing a bug?
  • Detail how the bug is invoked currently.
    call HydratingResultSet::current() on no data in current record.
  • Detail the original, incorrect behavior.
    it returns false.
  • Detail the new, expected behavior.
    it returns null, the "AbstractResultset" and "ResultSet" class returns null on no data, so it returns null for consistency/fix.
  • Base your feature on the master branch, and submit against that branch.
  • Add a regression test that demonstrates the bug, and proves the fix.
  • Add a CHANGELOG.md entry for the fix.

If this is considered a BC break, I can target to develop. Fixes #316

[ezimuel]

@samsonasik yes, this is a BC break. Please send it to develop. Thanks!

[samsonasik]

@ezimuel I've rebased against develop branch and change target to develop branch.

[weierophinney]

This repository has been closed and moved to laminas/laminas-db; a new issue has been opened at laminas/laminas-db#30.

[weierophinney]

This repository has been moved to laminas/laminas-db. If you feel that this patch is still relevant, please re-open against that repository, and reference this issue. To re-open, we suggest the following workflow:

• Squash all commits in your branch (git rebase -i origin/{branch})
• Make a note of all changed files (`git diff --name-only origin/{branch}...HEAD
• Run the laminas/laminas-migration tool on the code.
• Clone laminas/laminas-db to another directory.
• Copy the files from the second bullet point to the clone of laminas/laminas-db.
• In your clone of laminas/laminas-db, commit the files, push to your fork, and open the new PR.
  We will be providing tooling via laminas/laminas-migration soon to help automate the process.