DBOUpdate - Revision history

M.deluca: /* {{GVESB}} configuration */

2016-01-26T16:57:54Z

‎{{GVESB}} configuration

2016-01-25T22:53:55Z

‎{{GVESB}} configuration

2016-01-25T22:45:15Z

‎{{GVESB}} configuration

2015-01-03T13:10:44Z

2015-01-03T10:17:38Z

2015-01-02T14:29:40Z

2014-12-31T13:48:10Z

2012-11-12T12:19:22Z

‎{{GVESB}} configuration

2012-04-02T11:59:44Z

2012-04-02T11:25:59Z

‎{{GVESB}} configuration

@@ Line 190: / Line 190: @@
 As you can see in the above section you can make any queries update achievable with cypher language using the parameters in input.
-This DBO can be used also to delete elements present in the neo4j graph database usign the keyword and the related syntax of the cypher language.
+This DBO can be used also to delete elements present in the neo4j graph database usign the keyword and the related cypher language syntax.
-In the following example is shown a cypher query used to delete all nodes that meet the MATCH conditions and the related relationship:
+In the following example is shown a cypher query used to delete all nodes and the related relationships that meet the MATCH condition:
 <syntaxhighlight lang="XML"><?xml version="1.0" encoding="UTF-8"?>
 <?xml version="1.0" encoding="UTF-8"?>

@@ Line 189: / Line 189: @@
 </syntaxhighlight>
 As you can see in the above section you can make any queries update achievable with cypher language using the parameters in input.
 </div>

@@ Line 171: / Line 171: @@
 </xsl:stylesheet>
 </syntaxhighlight>
 </div>

@@ Line 115: / Line 115: @@
                      <xsl:value-of select="int:amount"/>
                  </xsl:element>
              </xsl:element>
          </xsl:element>

← Older revision		Revision as of 14:29, 2 January 2015
Line 16:		Line 16:

	In the second mode, the input XML (or its transformation) must contain the command (row) valid with all parameters (COL) required by the statement.		In the second mode, the input XML (or its transformation) must contain the command (row) valid with all parameters (COL) required by the statement.
		+
		+	It is used by [[DBOBuilder]].

	The following table shows the DBOUpdate attributes:		The following table shows the DBOUpdate attributes:

@@ Line 39: / Line 39: @@
 | output-data || optional || The default is the value of @name-Output.
 |}
 For example:

@@ Line 27: / Line 27: @@
 | name || required || DBOUpdate name
 |-
-| transformation || required || Transformation name
+| transformation || required || Transformation to be applied on the input data to obtain the internal XML commands.
 |-
 | force-mode || optional || (caller or xml2db) Force mode of the [[DBOBuilder#DBOs|DBO]], can be used in [[DBOBuilder]] whit more heterogeneous [[DBOBuilder#DBOs|DBOs]]. <br/> Mode:<br/> caller - inherit the mode of the caller<br/> xml2db - data entry mode

@@ Line 50: / Line 50: @@
         </DHVariables>
         <DBOUpdate class="it.greenvulcano.gvesb.datahandling.dbo.DBOUpdate"
-                name="PersonInsertFull" transformation="PersonInsertFull" type="dbo">
+                name="CCardPay" transformation="CCardPay" type="dbo">
-             <statement id="0" type="update">update PERSON set ID_CITY=? where ID=?</statement>
+               <statement id="0" type="update">
-             <statement id="1" type="update">update CREDIT_CARD  set CREDIT=?, ENABLED=? where ID=?</statement>
+                        update CREDIT_CARD  set CREDIT= CREDIT - ?
         </DBOUpdate>
   </DBOBuilder>
 </syntaxhighlight>
-Might contain the following sub-elements:
+According with the data present into the database, this statement will return the following XML:
 * [[Description]]
 * [[DHVariables]]
 * [[statement]]

@@ Line 29: / Line 29: @@
 | transformation || required || Transformation name
 |-
-| force-mode || optional || (caller|xml2db) Force mode of the [[DBOBuilder#DBOs|DBO]], can be used in [[DBOBuilder]] whit more heterogeneous [[DBOBuilder#DBOs|DBOs]]. <br/> Mode:<br/> caller - inherit the mode of the caller<br/> xml2db - data entry mode
+| force-mode || optional || (caller or xml2db) Force mode of the [[DBOBuilder#DBOs|DBO]], can be used in [[DBOBuilder]] whit more heterogeneous [[DBOBuilder#DBOs|DBOs]]. <br/> Mode:<br/> caller - inherit the mode of the caller<br/> xml2db - data entry mode
 |-
 | jdbc-connection-name || optional || DataSource JNDI name. <br/>  Override connection defined in [[DBOBuilder]].
 |-
-| ignore-input || optional || (true|false)  Tells the engine do not use the input data.
+| ignore-input || optional || (true or false)  Tells the engine do not use the input data.
 |-
 | input-data || optional || The default is the value of @name-Input.<br/>  Can be set as the @output-data of a preceding [[DBOBuilder#DBOs|DBO]] to use its output as input.