... |
... |
@@ -12,6 +12,17 @@ |
12 |
12 |
{{figure image="data_db_query_de.png"}}Configuration screen for creating a database query in: (1) list of existing DB queries, (2) editor for defining the SQL query, (3) settings of the DB query, (4) console for testing the DB query.{{/figure}} |
13 |
13 |
|
14 |
14 |
|
|
15 |
+{{html wiki="true"}} |
|
16 |
+<div class='xm-figure xm-float-right xm-clear-h2' data-alt='Configuration screen for creating a database query in: (1) list of existing DB queries, (2) editor for defining the SQL query, (3) settings of the DB query, (4) console for testing the DB query.'><div class='xm-figure-inner' style='width:310px'>{{lightbox image='data_db_query_de.png' width='300' group='$height' group='$group' title='Configuration screen for creating a database query in: (1) list of existing DB queries, (2) editor for defining the SQL query, (3) settings of the DB query, (4) console for testing the DB query.'/}}<div class='xm-figure-caption'>Configuration screen for creating a database query in: (1) list of existing DB queries, (2) editor for defining the SQL query, (3) settings of the DB query, (4) console for testing the DB query.</div></div></div> |
|
17 |
+{{/html}} |
|
18 |
+ |
|
19 |
+ |
|
20 |
+ |
|
21 |
+{{html wiki="true"}} |
|
22 |
+<div class='xm-figure xm-float-right xm-clear-h2' data-alt='Configuration screen for creating a database query in: (1) list of existing DB queries, (2) editor for defining the SQL query, (3) settings of the DB query, (4) console for testing the DB query.'><div class='xm-figure-inner' style='width:310px'>{{lightbox image='data_db_query_de.png' width='300' group='$height' group='$group' title='Configuration screen for creating a database query in: (1) list of existing DB queries, (2) editor for defining the SQL query, (3) settings of the DB query, (4) console for testing the DB query.'/}}<div class='xm-figure-caption'>Configuration screen for creating a database query in: (1) list of existing DB queries, (2) editor for defining the SQL query, (3) settings of the DB query, (4) console for testing the DB query.</div></div></div> |
|
23 |
+{{/html}} |
|
24 |
+ |
|
25 |
+ |
15 |
15 |
* Open the module "Database queries" and click "New" {{ficon name="plus-circle-outline"/}} in the header of the list (see [[figure>>||anchor="fig_data_db_query"]]). |
16 |
16 |
* The following data is needed for a Database query: |
17 |
17 |
** **Name**: A unique name for the database query |
... |
... |
@@ -22,7 +22,7 @@ |
22 |
22 |
|
23 |
23 |
The entered SQL statement is executed as a prepared statement, which prevents SQL injection attacks. You should not and need not use inverted commas (` or '). Also, you can use question marks ( ? ) as placeholders to build queries dynamically. |
24 |
24 |
|
25 |
|
-[[Variables>>doc:Formcycle.UserInterface.Variables.WebHome]] can be used in the SQL statements. |
|
36 |
+{{version major="6" minor="4" patch="0"/}} [[Variables>>doc:Formcycle.UserInterface.Variables.WebHome]] can be used in the SQL statements. |
26 |
26 |
|
27 |
27 |
== Using the database query == |
28 |
28 |
|
... |
... |
@@ -51,7 +51,7 @@ |
51 |
51 |
If possible the parameter //queryParameterValues// should be used for new projects instead of //delimiter// and //queryParameter// because //delimiter// will not be supported in a future version of {{formcycle/}}.|No |
52 |
52 |
{{/table}} |
53 |
53 |
|
54 |
|
-When accessing a database servlet from a form, always use the database URL contained in the global object //XFC_METADATA//, see also the [[metadata>>doc:Formcycle.Designer.Form.CodingPanel.ScriptTab.FormMetadata]]. For example: {{code language="javascript"}}XFC_METADATA.urls.datasource_db{{/code}}. |
|
65 |
+When accessing a database servlet from a form, always use the database URL contained in the global object //XFC_METADATA//, see also the [[metadata>>doc:Formcycle.FormDesigner.CodingPanel.ScriptTab.FormMetadata]]. For example: {{code language="javascript"}}XFC_METADATA.urls.datasource_db{{/code}}. |
55 |
55 |
|
56 |
56 |
Further we recommend you use the script function {{jsdoc page="xutil" name="getdataquery"/}}, so you do not have to setup the servlet request manually. The result of the database query is returned as //JSON//. |
57 |
57 |
|
... |
... |
@@ -79,7 +79,7 @@ |
79 |
79 |
|
80 |
80 |
== Selection form elements == |
81 |
81 |
|
82 |
|
-If you want to display the returned data as options of a [[selection element>>doc:Formcycle.Designer.Form.FormElements.Selection]], you can do so easily by opening the {{designer/}} and selecting the database query as the data source of the selection element. |
|
93 |
+If you want to display the returned data as options of a [[selection element>>doc:Formcycle.FormDesigner.FormElements.Selection]], you can do so easily by opening the {{designer/}} and selecting the database query as the data source of the selection element. |
83 |
83 |
|
84 |
84 |
{{info}} |
85 |
85 |
Queries that are used in selection elements must not have a question mark "?". Queries with a "?" are not offered as a data source for selection elements. |
... |
... |
@@ -89,7 +89,7 @@ |
89 |
89 |
Using the result of a database query as the data source a select element in the {{designer case="dat"/}}. |
90 |
90 |
{{/figure}} |
91 |
91 |
|
92 |
|
-The result of the database query is used to create the options of the [[selection element>>doc:Formcycle.Designer.Form.FormElements.Selection]] in the following order: |
|
103 |
+The result of the database query is used to create the options of the [[selection element>>doc:Formcycle.FormDesigner.FormElements.Selection]] in the following order: |
93 |
93 |
|
94 |
94 |
{{box}} |
95 |
95 |
Displayed value, submitted value, optional value 1, optional value 2, ... |