clean up connections in reverse order

[javornikolov]

Perform the connection cleanup and disposal in an order reverse of their initialization.

This is to resolve issues like setup/disposal of resources shared by multiple connections - e.g. profiler tables used by coverage when connections are to the same database schema.

This is an attempt to resolve #20

[jgebal]

Amazingly, this solves the issue 👍

[jgebal]

@javornikolov the #20 can be closed as resolved and PR #22 merged.
Out of topic.
I'm using ruby-plsql-spec to run cucumber tests too with shared config for both RSpec and Cucumber.
I was wondering on one of two options:

• contribute to ruby-plsql-spec and refacto it to make it Cukes ready.
• create a separate project.
  I'd opt for first solution, as it reuses many of existing code.

[javornikolov]

Amazingly, this solves the issue 👍

Coll. I'm merging this PR... Thanks for the feedback and for reporting the issue at first place!

I'm using ruby-plsql-spec to run cucumber tests too with shared config for both RSpec and Cucumber.
I was wondering on one of two options:

• contribute to ruby-plsql-spec and refactor it to make it Cukes ready.
• create a separate project.

I'd opt for first solution, as it reuses many of existing code.

Sounds nice. OK, let's try with 1st option and see where it will lead us.