Benjamin,
Thank you for taking the time to explain this to me and for your efforts in identifying the cause. I'm really looking forward to exploring this feature in version 2024.3 - it has the potential to be like a game changer for dynamic integration of external data.
Andreas
@Benjamin De Boe your hints helped me a lot! I tested the THROUGH command via the SQL shell and it WORKS there! It also works via the SQL command window in the management portal! As far as I understand it, neither of them use a standard SQL interface (JDBC\ODBC), right?
Because it does not work when I send the command to IRIS via JDBC!
I have used the latest driver known to me (intersystems-jdbc-3.9.0.jar 555kb).
I have also checked which driver was supplied with InterSystems IRIS version 2024.3.0.206. A new driver could have been included there, but the JDBC driver is identical to InterSystems IRIS version 2024.2.0.247 both in name and in the size of the file.
You may be able to try your test environment via JDBC to see if you have the same problem. Thanks!
Andreas
The container image IMAGE=containers.intersystems.com/intersystems/iris-community:latest-cd from today also contains just the intersystems-jdbc-3.10.0.jar driver
The db version of this container image reports as "InterSystems IRIS Version 2024.3.0.209", this is the release from here General Availability of InterSystems IRIS, InterSystems IRIS for Health, right?!
@Benjamin De Boe maybe you can clearify from where this version of the iris-driver-distribution repository on GitHub -> intersystems-jdbc-3.10.1.jar. came from?
Andreas