5.1 SQL Server Engine
<SqlServerMultiThread> </SqlServerMultiThread>Configuration parameters for the engine in a multi-threaded environment. If SDX objects are to be used in threads, this option must be set to true.
5.2 PostgreSQL Engine
<PGSQLConnPoolSize></PGSQLConnPoolSize>Configuration parameters for the engine in a multi-threaded environment. 0 represents not using a connection pool. If SDX objects are to be used in threads, the parameter should be set according to actual requirements. It is recommended to set it to a value greater than 1 and match it with the number of connections, which is beneficial for performance improvement. Note that this parameter is static; if modified, the program needs to be restarted.
5.3 Schema and Dataset Name Connector
<SchemaJoin></SchemaJoin>This tag is used to set the connector between the Schema name (non-default Schema) and the dataset name when there are multiple Schemas in the database. The connector only supports underscore _ and period .. It is applicable to PostGIS data sources. For example: There are two Schemas under a PostGIS data source, Public (default Schema) and Sch, and both Schemas contain spatial data (the spatial data table name under Sch is dt). When the tag is set to <SchemaJoin>.</SchemaJoin>, the spatial data table dt will be registered to the data source with the dataset name Sch.dt.
5.4 Field Name Case Sensitivity
<FieldNameCaseSensitive></FieldNameCaseSensitive>This tag is used to control the case sensitivity of field names, effective from SuperMap iDesktopX 2025 R2 version. When set to True, field names containing uppercase letters will retain their original case; when set to False, field names will be uniformly converted to lowercase. The default value of this parameter is False. It is applicable to PostGIS series data sources, including: PostGIS, KingBase, HighGoDB, SHENTONG, POLARDBGanos data sources. Note that: 1. This parameter is only effective when using the SDX connection method; it does not take effect through JDBC-PostGIS connection. 2. If field names containing uppercase letters are created on a platform set to True, and then the data set is opened on a platform set to False or on a version prior to 2025 R2, the field names will all be displayed in lowercase.