Objectives
When using the Alkaes Database Client , some settings will be welcomed to enhance your experience.
How to configure these settings
Access Settings page
As all Alkaes plugins, its Settings are managed through a dedicated plugin. To access them, process as follow :
- Go to Manage Apps administraiion menu
- Select in Alkaes Settings Section the menu Manage Settings,
- then select Database Client Settings,
Manage Settings
The implemented settings are the following ...
| Settings | Goal | Explanation |
|---|---|---|
| If enabled, the build of SQL Statement quotes table name | Depending on SGBD used for your Jira, the reference of Database Objects have to follow the correct case. The access may required or not to see these objects quoted in SQL SELECT * FROM "AO_60DB71_SPRINT" SSELECT * FROM AO_60DB71_SPRINT |
| If Apply row limit enabled, a Default Row Limit is applied on SQL Statements | When querying the Database, if you are aware with the model, you may write SQL Statement with missing Join criteria or Where clauses. To avoid to return to large volume of data, you can opt to use the Row Limit clause. This settings helps you to apply the clause by default in the built statement. SELECT * FROM "AO_60DB71_SPRINT" limit 100 |
| If Metadata Mode via JDBC is set to Yes, the Metadata is loaded via DatabaseMetaData Class implemented in JDBC, If No, the Metadata is loaded via SQL Statements (available only for supported DBMS) | See details in Database Scheme. |
| When Metadata Mode via JDBC is set to Yes and If the Additional Objects Type to display option is let Empty, only Tables are retained when getting Shema. If expected, add comma separated list of additional Object Types (Relevant when Metadata Mode via JDBC = Yes) | May be useful, if want explorer other Database Objects. Available only with Oracle and PostgreSQL. |
| If empty, not filtering is applied when getting Tables, and you will see all Tables visible to you Jira account. In some cases, you will have to explicitly specify which schema you wan to see by specifying a schema or list of schema (using a comma separated list of Schema) | To use when you see Table that are not par of Jira, from others Schema. |