Resolve column name in ResultSetIterator.set

[rootvector2]

set passes the raw lower-cased property name to ResultSet.updateObject while the read path resolves it through getColumnName first, so under the default lowerCase an update to a mixed-case column targets the wrong column or throws on a case-sensitive driver; found diffing the get and set paths against getObject.

• Read the contribution guidelines for this project.
• Read the ASF Generative Tooling Guidance if you use Artificial Intelligence (AI).
• I used AI to create any part of, or all of, this pull request. Which AI tool was used to create this pull request, and to what extent did it contribute?
• Run a successful build using the default Maven goal with mvn; that's mvn on the command line by itself.
• Write unit tests that match behavioral changes, where the tests fail if the changes to the runtime are not applied. This may not always be possible, but it is a best practice.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• Each commit in the pull request should have a meaningful subject line and body. Note that a maintainer may squash commits during the merge process.

[garydgregory]

Hi @rootvector2
Please see my comment.

[garydgregory]

@rootvector2
Use an AtomicReference instead of the old-school array hack ;)

[garydgregory]

@rootvector2 Ping 🔔