Dbvis.xml download

The figure shows the use of separators and two fields that extend to the full width of the action dialog. The separators for Parameters and Source are here used as alternatives to labels for the fields below them. The grid input style is presented as a grid with user controls to add , remove and move rows.

The columns that should appear in the grid are defined by using any of the primitive styles: text , number , password , check , list and radio. The grid style is useful for data that allows the user to define multiple entries. Examples are, defining columns that should appear in a table index, setup data files for a tablespace or databank. This example show a grid style definition that will ask the user for parameters that will be part of a create procedure action.

The sub elements for the grid style is different from the other input styles as it accepts nested Input elements. These input styles define what columns should appear in the grid and the first input style will appear to the leftmost and the last in the rightmost column. This example doesn't specify the label attribute as we want the grid to extend the full width of the actions dialog.

The grid style use the Arg elements to customize the appearance and function of the field. The following arguments are handled by the grid style:. The resulting parameter list is created automatically by the control and is available in the variable name specified in the example to be parameters.

It is used to process the data for every row in the grid. Let's say that the output must contain the word " default " if the value in a column named Default is entered. SetVar is used to handle this:. The default input value is here evaluated and if it is not empty the " default " text s prefixed to the value of the default value. The SetVar element is used to do conditional processing and create new variables based on the content of other variables or static text.

In this case it is quite easy to map the user field to an Input element for the action since it is a required field. The question arise for password which is optional. The identified by clause should only be part of the final SQL if the password is entered by the user. The solution for this scenario is to use the SetVar element. Here is the complete action definition:. The expression in the example above checks whether the password variable is empty. The Confirm element is displayed to the user when a request to Execute the action is made.

If there are only read-only input fields in the action, this message is displayed in the body of the action dialog. Otherwise the message is displayed in a confirmation dialog. The Result element is optional and if specified, it is shown in a dialog after successful execution. The Message element can be used to specify an action message that will appear at the top of the action window. DbVisualizer 9. Users Guide.

Browse pages. A t tachments 5 Page History. Jira links. This attribute is required and valid only for top level ActionGroup elements not nested ActionGroup elements. This attribute have no effect on top level ActionGroup elements action drop drop is useful when extending another database profile to remove the ActionGroup and all its child elements order-before Specifies the order of this ActionGroup among a collection of ActionGroup elements located at the same level.

It can either be an index starting at 0 first or a node type. Attribute Value Description id Every Action element must have a unique id which is not only unique in the current profile but also with all id's in extended profiles. The recommended format is profileName-actionGroupType-action. Ex: oracle-table-drop. See following sections for more details hideif There may be situations when an Input element should be dropped due to a condition.

The hideif attribute is used to express a condition which is evaluated when the action is initialized. Attribute Description name The name of the new variable value Should contain the expression that will be evaluated. The expression is based on the OGNL toolkit. This is an expression library that mimics most of what is being supported by Java. Variables are referenced as variableName action This attribute is optional and can have any of the following values: show - default and indicates that the variable and its value will appear in node-form viewers hide - the variable will not display in node-form viewers drop - the SetVar element is not evaluated when actions is being processed runwheninit - runs the SetVar only during initialization of the action before window is displayed.

Result elements are currently not displayed in DbVisualizer. It is however recommend that you specify these as they will most likely appear in some way or another in a future version. No labels. Powered by Atlassian Confluence 6. This defines what object type the ActionGroup is mapped to. This attribute is required for nested ActionGroup elements and is the label displayed in the sub menu. This attribute have no effect on top level ActionGroup elements.

Specifies the order of this ActionGroup among a collection of ActionGroup elements located at the same level. Installer Type. With Java. Windows bit. Download No java. Download With java. View other versions Change version. Latest Version: DbVisualizer Read DbVisualizer reviews on G2! System requirements. Mail me when new features are announced. The user may select any cells in the grid and choose a custom menu item.

It is only the actual rows that are picked from the selection as the columns are predefined by the menuItem declaration. These define that the first variable represents a schema variable while the second defines an object. This is needed for DbVisualizer to determine whether delimited identifiers should be used and if identifiers should be qualified, as defined in the connection properties for the database.

Some result sets may contain wide columns. The following parameter sets an initial maximum width for all columns in the grid. The text viewer presents data from one column in a result set in a text browser read only. This viewer is typically used to present large chunks of data, such as source code, SQL statements, etc. If the result set contain several rows, the text viewer reads the data in the column for each row and present the combined data.

And here is a screenshot of the Source tab based on the previous definition. By default, the text viewer uses the data in first column. This behavior can be controlled by using the dataColumn input parameter. Simply specify the name of the column in the result set or its index starting at 1 from the left. The formatSQL input parameter is used to control whether formatting should be made automatically when the data first displayed.

If formatSQL is not specified, no initial formatting is made. For a result set containing multiple rows and all rows should be displayed in a text viewer, the newline parameter define the character s that should separate the rows in the viewer.

By default there is no newline sequence between multiple rows. The form viewer displays row s from a result set in a form. If several rows are in the result, they are presented in a list. Selecting one row from the list presents all columns and data for that row in a form. The node-form viewer presents all data associated with the selected DataNode variables.

Here is a sample of the XML for the node-form viewer:. There may be data associated with the object that you don't want to present in the node form.

The hidecolumn input parameter control what data for the object that should be invisible and you may repeat this option as many times you like to handle multiple variables that shouldn't be displayed. The table-refs viewer shows the references graph for the current object this must be an object supporting referential integrity constraints, such as a Table ,. The tables-refs viewer shows the references graph for several tables in the result set the result set must contain objects supporting referential integrity constraints, such as a Table.

Here is a sample of the XML for the tables-refs viewer:. The table-data viewer shows the data for a table in a grid with various features such as filtering and editing if licensed functionality. It is important that the Database Type in the connection setup is properly set to match the database being accessed. The reason is that the identifiers schema, database, table are delimited automatically. Delimiters are database specific and if having the wrong database type set it may result in an error getting the result.

The default strategy for the table-data viewer is to automatically check whether the data can be edited or not. If editing is allowed a few related buttons will appear in the toolbar.

However, sometimes you may want to disable editing completely for the table-data viewer. Do this with the following input element:.