Joget DX 8 Stable Released
The stable release for Joget DX 8 is now available, with a focus on UX and Governance.
JDBC Datalist Action allows you to perform SQL queries on one (a row action) or more records (a bulk action) in your datalist. You can specify which database to perform the SQL function, either the current Joget database (default datasource) or a custom datasource (external database).
JDBC Datalist Action can be used to delete records or perform an update on one or more records based on user selection in the datalist checkboxes.
Name | Description | |
---|---|---|
Label | Datalist button label. | Figure 1 : JDBC Action Menu Figure 2 : JDBC Datalist Action |
Confirmation Message | Confirmation message before performing action, for example "Are you sure?". | |
Datasource |
| |
Custom JDBC Driver | Custom JDBC Driver. This field is required when Custom Datasource is selected in Datasource above. | |
Custom JDBC URL | Custom JDBC URL. This field is required when Custom Datasource is selected in Datasource above. | |
Custom JDBC Username | Custom JDBC Username. This field is required when Custom Datasource is selected in Datasource above. | |
Custom JDBC Password | Custom JDBC Password. This field is required when Custom Datasource is selected in Datasource above. Test the connection parameters Click on the "Test Connection" button at the bottom of the page to quickly test out your configurations. | |
Query | Insert your SQL statement here. Use syntax like {id} in query to inject the selected row key. Use {uuid} to generate a unique id (or primary key). Examples: Example INSERT INTO app_fd_sample (id, c_clicked) VALUES ( {uuid}, {id} ) Example UPDATE app_fd_sample SET c_clicked = CONCAT(c_clicked, ',', {id}) WHERE id = {id} Example DELETE FROM app_fd_myTable WHERE id = {id} How it works? For database tables created by Joget Forms, Joget adds a "c_" in front of table column names and "app_fd_" in front of database table names. The special parameters {id} and {uuid} will be replaced with actual values through the use of PreparedStatement. As you can see from the example above, there is no need to encapsulate both of these special keywords with quotes. |