@geraldodev OK, I've pushed an update to master that implements the above. It's not documented or tested yet (beyond what I've done in the REPL).

You may find Oracle requires additional options to support calling getRow but let me know whatever you find.

(I have not yet tested that the metadata-driven protocol stuff survives partition-all but I will make sure that's in the test suite!)

Thank you @seancorfield. I'll let you know how it goes.

And thank you for supporting jdbc and evolving it with next-jdbc.

Added tests that confirm row-number and column-names work on bare rows, realized rows (via datafiable-row), and they survive partition-all 🙂 Now I just need to document all of this new stuff...

@geraldodev Those new functions are available in release 1.0.445 on http://clojars.org

If folks have suggestions for additional functions that would be useful in the new InspectableMapifiedResultSet protocol (for use in reducing over plan), alongside the new row-number and column-names functions, feel free to discuss them here or via issues on the next.jdbc repo...