Creates a database reader based on selected spatial and attribute constraints to be used when reading the data. These constraints are invoked via FME Objects.
Readers are often used to access datasets with millions of features. By using setConstraints() via FME Objects, an optimized query can occur where we limit the amount of data to be read. This can be useful when a dataset is very large or slow to access. A list with the possible types of constraints can be found here: https://docs.safe.com/fme/html/FME_setConstraints/index.html
This transformer accepts any kind of features, but for each feature sent into the TestSuite.DatabaseConstraintQuerier a new database reader is created.
Features that have been read from the database.
The name of the database to read.
The type (format) of the database.
The directives needed to connect to the database and constraints calls.
The Reader Creation and Constraints Arguments parameter support the following list of switches:
--<directivename> <directivevalue> (Directive key/value pairs)
-props <category> (Property category to fetch - these are UniversalReader properties - we can get native properties using fmeobjects but haven't bothered)
X Y X Y ... (one or more points to define Envelope query - easier to simply set the geometry on the Initiator feature)
<constraintname> <constraintvalue> (Constraint key/value pairs)
READER DATASET = testsuitedb
READER TYPE = POSTGIS
READER CREATION AND CONSTRAINTS ARGUMENTS = --HOST bt-db-rhes3 --USER_NAME postgres --PASSWORD postgres --PORT 5432 fme_search_type fme_all_features fme_feature_type postgres.PR18099 fme_where 'test_index = 1'
Using a set of menu options, transformer parameters can be assigned by referencing other elements in the workspace. More advanced functions, such as an advanced editor and an arithmetic editor, are also available in some transformers. To access a menu of these options, click
beside the applicable parameter. For more information, see Transformer Parameter Menu Options.
TestSuite Tools (Safe Internal)