-
transaction
Wrapper for a single transaction. Transactions allow several files or blocks of statements to be executed using the same PDO connection and commit operation in between.
Table 113. Attributes
Name Type Description Default Required tsrcfile
String
File with statements to be run as one transaction n/a No
-
fileset
Files containing SQL statements.
-
filelist
Files containing SQL statements.
-
formatter
The results of any queries that are executed can be printed in different formats. Output will always be sent to a file, unless you set the
usefile
attribute tofalse
. The path to the output file can be specified by theoutfile
attribute; there is a default filename that will be returned by the formatter if no output file is specified.There are three predefined formatters - one prints the query results in XML format, the other emits plain text. Custom formatters that extend phing.tasks.pdo.PDOResultFormatter can be specified.
Table 114. Attributes
Name Type Description Default Required type
String
Use a predefined formatter (either xml
orplain
).n/a One of these attributes is required. classname
String
Name of a custom formatter class (must extend phing.tasks.ext.pdo.PDOResultFormatter). n/a usefile
Boolean
Boolean that determines whether output should be sent to a file. true
No outfile
File Path to file in which to store result. Depends on formatter No showheaders
Boolean
(only applies to plain formatter) Whether to show column headers. false
No coldelim
String
(only applies to plain formatter) The column delimiter. , No rowdelim
String
(only applies to plain formatter) The row delimiter. \n No encoding
String
(only applies to XML formatter) The xml document encoding. (PHP default) No formatoutput
Boolean
(only applies to XML formatter) Whether to format XML output. true
No