Click on the "Test Connection" button at the bottom of the page to quickly test out your configurations.

If a column name contains reserved keywords, do ensure it is encapsulated properly.

For example for MySQL, if the column identifier itself contains a dot symbol ( . ), it should be encapsulated like this:

SELECT `myAppName.myColumn` FROM app_fd_myTable;

INSERT INTO
   app_fd_sample (id, c_clicked) 
VALUES
   (
      {uuid}, {id} 
   )

UPDATE
   app_fd_sample 
SET
   c_clicked = CONCAT(c_clicked, ',', {id}) 
WHERE
   id = {id}

DELETE
FROM
   app_fd_myTable 
WHERE
   id = {id}

• For database tables created by Joget Forms, Joget adds a "c_" in front of table column names (or "t_" if your column name starts with a number) and "app_fd_" in front of database table names.
• If you use environment hash variables to store SQL query strings, in your hash variable, use "?noescape" to escape SQL query strings in JDBC binders to prevent the "<>" "not equal" operator from being converted, i.e. disables XSS prevention checking. Read here for more information..

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.