complexType "etl:FilterType"
Namespace:
Content:
complex, 6 attributes, 1 element
Defined:
globally in etl.xsd, see XML source
Includes:
definitions of 6 attributes and 1 element
Used:
XML Representation Summary
<...
    className
 = 
("RunFilterStrategy" | "ModifiedSinceFilterStrategy" | "SelectAllFilterStrategy")
    fkColumnName
 = 
string
    pkColumnName
 = 
string
    runTable
 = 
string
    runTableSchema
 = 
string
    timestampColumnName
 = 
string
    >
   
Content: 
etl:deletedRowsSource?
</...>
Content Model Elements (1):
All Direct / Indirect Based Elements (1):
Known Usage Locations
XML Source (see within schema source)
<complexType name="FilterType">
<all>
<element minOccurs="0" name="deletedRowsSource" type="etl:DeletedRowsSourceObjectType">
<annotation>
<documentation>
Defines a query with a list of rows to delete from the target in this incremental run.&lt;br/&gt;
Timestamp or run filter values against the delete rows source are tracked independently from the values in the&lt;br/&gt;
original source query. I.e., there could be no new records in the source query, but new records in the delete rows source&lt;br/&gt;
will still be found and deleted from the target.
</documentation>
</annotation>
</element>
</all>
<!-- <all>
<element name="properties" type="etl:PropertiesType" minOccurs="0"/>
</all>
-->
<attribute name="className" type="etl:FilterClassType" use="optional"/>
<!-- TODO: temp removing this attribute until it is implemented. Intended to be an in-app configurable override to the filter strategy
<attribute name="selectAll" type="boolean" use="optional"/>
-->
<!-- org.labkey.di.filters.ModifiedSinceFilterStrategy -->
<attribute name="timestampColumnName" type="string" use="optional"/>
<!-- org.labkey.di.filters.RunFilterStrategy -->
<attribute name="runTableSchema" type="string" use="optional"/>
<attribute name="runTable" type="string" use="optional"/>
<attribute name="pkColumnName" type="string" use="optional"/>
<attribute name="fkColumnName" type="string" use="optional"/>
</complexType>
Attribute Detail
className
Type:
Use:
optional
Defined:
locally, within (this) etl:FilterType complexType
XML Source (see within schema source)
<attribute name="className" type="etl:FilterClassType" use="optional"/>

fkColumnName
Type:
string, predefined
Use:
optional
Defined:
locally, within (this) etl:FilterType complexType
XML Source (see within schema source)
<attribute name="fkColumnName" type="string" use="optional"/>

pkColumnName
Type:
string, predefined
Use:
optional
Defined:
locally, within (this) etl:FilterType complexType
XML Source (see within schema source)
<attribute name="pkColumnName" type="string" use="optional"/>

runTable
Type:
string, predefined
Use:
optional
Defined:
locally, within (this) etl:FilterType complexType
XML Source (see within schema source)
<attribute name="runTable" type="string" use="optional"/>

runTableSchema
Type:
string, predefined
Use:
optional
Defined:
locally, within (this) etl:FilterType complexType
XML Source (see within schema source)
<attribute name="runTableSchema" type="string" use="optional"/>

timestampColumnName
Type:
string, predefined
Use:
optional
Defined:
locally, within (this) etl:FilterType complexType
XML Source (see within schema source)
<attribute name="timestampColumnName" type="string" use="optional"/>
Content Element Detail
etl:deletedRowsSource
Type:
Defined:
locally, within (this) etl:FilterType complexType
Defines a query with a list of rows to delete from the target in this incremental run.<br/> Timestamp or run filter values against the delete rows source are tracked independently from the values in the<br/> original source query. I.e., there could be no new records in the source query, but new records in the delete rows source<br/> will still be found and deleted from the target.
XML Source (see within schema source)
<element minOccurs="0" name="deletedRowsSource" type="etl:DeletedRowsSourceObjectType">
<annotation>
<documentation>
Defines a query with a list of rows to delete from the target in this incremental run.&lt;br/&gt;
Timestamp or run filter values against the delete rows source are tracked independently from the values in the&lt;br/&gt;
original source query. I.e., there could be no new records in the source query, but new records in the delete rows source&lt;br/&gt;
will still be found and deleted from the target.
</documentation>
</annotation>
</element>

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:
  • To configure the generated documentation so much as you want. Thanks to our template technology, it was possible to support more than 300 template parameters (working the same as "options" of an ordinary doc-gen), which will give you an unprecedented control over the generated content!
  • To use certain features disabled in the free mode (such as the full documenting of substitution groups).
  • To enable/disable documenting of the initial, imported, included and redefined XML schemas selectively.
  • To document local element components both globally and locally (similar to attributes).
  • To enable/disable reproducing of namespace prefixes.
  • To format your annotations with XHTML tags and reproduce that formatting both in HTML and RTF output.
  • To insert images in your annotations using XHTML <img> tags (supported both in HTML and RTF output).
  • To use PlainDoc.tpl main template to generate all the XML schema documentation in the form of a single HTML file.
  • To use the same template to generate the incredible quality RTF documentation.
  • To document only selected XML schema components specified by name.
  • To remove this very advertisement text
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/