sql

All things SQL and JDBC...
seancorfield 2020-05-23T00:12:20.080Z

@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).

seancorfield 2020-05-23T00:13:55.080900Z

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

seancorfield 2020-05-23T00:14:35.081600Z

(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!)

2020-05-23T00:15:06.082Z

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

2020-05-23T00:21:22.082800Z

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

seancorfield 2020-05-23T03:35:51.083900Z

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...

seancorfield 2020-05-23T18:26:37.084400Z

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

👍 1
seancorfield 2020-05-23T18:29:47.086200Z

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...