[
https://issues.apache.org/jira/browse/DERBY-5861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-5861:
---------------------------------
Attachment: DerbyPropertyViewer.java
Attaching DerbyPropertyViewer, a table function which shows the settings of the
derby properties. Here is an ij script which shows how to use this table
function:
connect 'jdbc:derby:memory:db;create=true';
create function derbyPropertyViewer()
returns table
(
prop_name varchar( 32672 ),
prop_value varchar( 32672 )
)
language java parameter style derby_jdbc_result_set
reads sql data
external name 'DerbyPropertyViewer.derbyPropertyViewer';
select * from table( derbyPropertyViewer() ) t
where prop_value is not null;
> Provide a diagnostic table function which lets DBOs view the Derby properties
> understood by their database.
> -----------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5861
> URL: https://issues.apache.org/jira/browse/DERBY-5861
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 10.10.0.0
> Reporter: Rick Hillegas
> Attachments: DerbyPropertyViewer.java
>
>
> Currently there is no way for the DBO to verify what the database thinks the
> derby properties are. We could provide a diagnostic table function to show
> this information. By default only the DBO should be able to run this table
> function. I will attach a crude workaround.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira