We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When using DBeaver with InterSystems IRIS and asking to see the definition (source code) of a view, we get nothing:
Community 22.3.0
Mac and Windows
InterSystems IRIS 2022.2
Create a simple view in InterSystems IRIS Connect DBEaver to the namespace Ask to see the definition of the view
No response
The text was updated successfully, but these errors were encountered:
Hello @amirsamary
Because it is not supported yet, if you know the query to get the view definition from a database - please, share it with us.
Sorry, something went wrong.
Currently this has to go through an ObjectScript API call: %SYSTEM.SQL.Schema:ExportDDL(). We can call this through the com.intersystems.jdbc.IRIS:classMethodStatusCode() method on the JDBC driver
I forgot the much easier alternative available from the catalog views:
SELECT View_Definition FROM INFORMATION_SCHEMA.VIEWS where TABLE_NAME='AssetBreakDown' and TABLE_SCHEMA='halp_view'
Thanks @amirsamary for refreshing my memories! ;-)
dbeaver#18437 Support of InterSystems IRIS VIEW definition
5655264
To implement getViewDDL I added a plugin for InterSystems IRIS
dbeaver#18437 Removed unnecessary logging and simplified pom
1c201d0
Successfully merging a pull request may close this issue.
Description
When using DBeaver with InterSystems IRIS and asking to see the definition (source code) of a view, we get nothing:
DBeaver Version
Community 22.3.0
Operating System
Mac and Windows
Database and driver
InterSystems IRIS 2022.2
Steps to reproduce
Create a simple view in InterSystems IRIS
Connect DBEaver to the namespace
Ask to see the definition of the view
Additional context
No response
The text was updated successfully, but these errors were encountered: