Tables |
  
|
Tables |
|
The entire database Tables used for querying and/or for providing Lookup functionality are stored here. A list of Table elements can be configured.
Tables - General category
Property |
Description |
Name |
Full name of Table. If using relational database system (RDBMS), schema and table name of the database table definition have to be used (i.e. SCHEMA.TABLENAME). Some RDBMS (SQL Server) require additional information on the DB-Owner (OWNER.SCHEMA.TABLENAME). Note: Oracle DB requires case sensitive schema and table names. |
Reference to Database connection |
Database connection to be used for actually connecting to the database Table using JDBC. Note: All connections configured under Database connections will be available in den drop down list. See chapter Database Connection for more information about configuration of database connections. |
Display Name (GUI) |
Alias Table name shown in the WebOffice 10 R3 client. |
Show null values? |
Specifies whether to show null values ("Yes") or not ("No") in the result display. |
Use joined Layer? |
Specifies whether the join element of a layer search result configuration is used for displaying a layer search result (attribute data as well as objects in the map) when searching on table fields. Note: To use this functionality, a join from the layer (Layer queries) to this table is the precondition. This way you can search on the tables data and get the attributes and spatial information of the joined layer (layer the join is based on). Note: Currently, it is not possible to restrict a table base search to the current spatial extent even if this parameter is set to "Yes". |
Table - General category
In order to configure all relevant aspects for Table search and result display a set of configuration elements should be taken into consideration:
•Query: Specify generic query (Query Builder) behavior,
•Query builder field list: Specify all available search fields. Search fields can be used in either
•Query Builder or
•Predefined query
•List of predefined queries: Multiple Predefined queries can be configured. This makes the search & find process much easier for the user,
•List of search result views: Multiple Search results can be configured to provide different ‘views’ on the data.
See chapter Layer queries for details.
Query element – specify generic query (Query builder) behavior
Search field list and Search field
List of predefined queries
Note: The parameters "Permit spatial attributive search function?" and "Spatial attributive Search activated per default?" currently only work with spatial feature classes, i.e. the above mentioned parameters have no function for attributive table queries.
List of search result views