Namespace: |
|
Content: |
complex, 11 attributes, 2 elements |
Defined: |
globally in etl.xsd, see XML source |
Includes: |
definitions of 2 attributes |
Used: |
at 1 location |
XML Representation Summary | |||||
<... | |||||
containerFilter | = |
("Current" | "CurrentWithUser" | "CurrentAndFirstChildren" | "CurrentAndSubfolders" | "CurrentAndSiblings" | "CurrentOrParentAndWorkbooks" | "CurrentPlusProject" | "CurrentAndParents" | "CurrentPlusProjectAndShared" | "AssayLocation" | "WorkbookAndParent" | "StudyAndSourceStudy" | "AllFolders") | |||
deletedSourceKeyColumnName | = |
string | |||
queryName | = |
string | |||
remoteSource | = |
string | |||
runColumnName | = |
string | |||
schemaName | = |
string | |||
sourceContainerPath | = |
string | |||
sourceTimeout | = |
integer | |||
targetKeyColumnName | = |
string | |||
timestampColumnName | = |
string | |||
useTransaction | = |
boolean : "true" | |||
> | |||||
|
|||||
</...> |
Type Derivation Tree etl:DeletedRowsSourceObjectType (extension) |
<complexType name="DeletedRowsSourceObjectType"> <complexContent> <annotation> <documentation> The column in the deletedRowsSource which holds the key values to delete in the target. If not specified, the PK values of the delete query is used. </documentation> </annotation> </attribute> <annotation> <documentation> The column in the target query corresponding to the deleted key values. If not specified, we assume the PK of the target query.<br/> If a non-PK column is specified, the delete values will be used as lookups to map back to the corresponding PK values in the target. </documentation> </annotation> </attribute> </extension> </complexContent> </complexType> |
Type: |
|
Use: |
optional |
Defined: |
<attribute name="containerFilter" type="cv:containerFilterType" use="optional"> <annotation> <documentation> Specify the type of container filter to use on the source query. </documentation> </annotation> </attribute> |
Type: |
string, predefined |
Use: |
optional |
Defined: |
<attribute name="deletedSourceKeyColumnName" type="string" use="optional"> <annotation> <documentation> The column in the deletedRowsSource which holds the key values to delete in the target. If not specified, the PK values of the delete query is used. </documentation> </annotation> </attribute> |
Type: |
string, predefined |
Use: |
required |
Defined: |
<attribute name="queryName" type="string" use="required"/> |
Type: |
string, predefined |
Use: |
optional |
Defined: |
<attribute name="remoteSource" type="string" use="optional"/> |
Type: |
string, predefined |
Use: |
optional |
Defined: |
<attribute name="runColumnName" type="string" use="optional"> <annotation> <documentation> Override the column name set on a RunFilter incremental filter. </documentation> </annotation> </attribute> |
Type: |
string, predefined |
Use: |
required |
Defined: |
<attribute name="schemaName" type="string" use="required"/> |
Type: |
string, predefined |
Use: |
optional |
Defined: |
<attribute name="sourceContainerPath" type="string" use="optional"> <annotation> <documentation> Container path for doing cross-container ETLs. If not entered, defaults to the container where the ETL is running. </documentation> </annotation> </attribute> |
Type: |
integer, predefined |
Use: |
optional |
Defined: |
<attribute name="sourceTimeout" type="integer" use="optional"/> |
Type: |
string, predefined |
Use: |
optional |
Defined: |
<attribute name="targetKeyColumnName" type="string" use="optional"> <annotation> <documentation> The column in the target query corresponding to the deleted key values. If not specified, we assume the PK of the target query.<br/> If a non-PK column is specified, the delete values will be used as lookups to map back to the corresponding PK values in the target. </documentation> </annotation> </attribute> |
Type: |
string, predefined |
Use: |
optional |
Defined: |
<attribute name="timestampColumnName" type="string" use="optional"> <annotation> <documentation> Override the column name set on a ModifiedSinceFilter incremental filter. </documentation> </annotation> </attribute> |
Type: |
boolean, predefined |
Use: |
optional |
Default: |
"true" |
Defined: |
<attribute default="true" name="useTransaction" type="boolean" use="optional"> <annotation> <documentation> Wrap selecting from source query in a transaction. Only used for simple query transform types. </documentation> </annotation> </attribute> |
Type: |
etl:SourceColumnsType, complex content |
Defined: |
<element maxOccurs="1" minOccurs="0" name="sourceColumns" type="etl:SourceColumnsType"/> |
Type: |
etl:SourceFiltersType, complex content |
Defined: |
<element maxOccurs="1" minOccurs="0" name="sourceFilters" type="etl:SourceFiltersType"/> |
This XML schema documentation has been generated with DocFlex/XML RE 1.7.2 using DocFlex/XML XSDDoc 2.1.0 template set. DocFlex/XML RE is a reduced edition of DocFlex/XML, which is a tool for programming and running highly sophisticated documentation and reports generators by the data obtained from any kind of XML files. The actual doc-generators are implemented in the form of special templates that are designed visually using a high quality Template Designer GUI basing on the XML schema (or DTD) files describing the data source XML. DocFlex/XML XSDDoc is a commercial template application of DocFlex/XML that implements a high-end XML Schema documentation generator with simultaneous support of framed multi-file HTML, single-file HTML and RTF output formats. (More formats are planned in the future). A commercial license for "DocFlex/XML XSDDoc" will allow you:
Once having only such a license, you will be able to run the fully-featured XML schema documentation generator both with DocFlex/XML SDK and with DocFlex/XML RE, which is a reduced free edition containing only the template interpretor / output generator. No other licenses will be required! But this is not all. In addition to it, a commercial license for DocFlex/XML SDK will allow you to modify the XSDDoc templates themselves as much as you want. You will be able to achieve whatever was impossible to do with the template parameters only. And, of course, you could develop any template applications by your own! Please note: By purchasing a license for this software, you not only acquire a useful tool, you will also make an important investment in its future development, the result of which you could enjoy later by yourself. Every single your purchase matters and makes a difference for us! To buy a license, please follow this link: http://www.filigris.com/shop/ |