Datasource Supports Specifying Schema

Function Description

Schema is a logical container in a database used to organize and manage objects (such as tables, views, indexes, etc.). Similar to "folders" in a file system, it is used to classify and isolate database objects, enhancing the flexibility of permission control.

  • Applicable Databases: PostGIS, POLARDBGanos, KingBase, HighGoDB, SHENTONG, Vastbase.

Setting Schema When Opening a Datasource

Setting Instructions

Supports specifying a Schema name when opening a datasource, which is empty by default.

  • If a Schema is specified, write operations (such as creating a dataset, importing a dataset) will default to that Schema.
  • If not specified, the Schema where the datasource is located will be used by default.

Permission Instructions

After the datasource is opened, datasets under all Schemas for which the user has read or edit permissions will be displayed. The actual permissions of the datasets depend on the read and write permissions of the connected user for the corresponding Schema and data, and are unrelated to the Schema specified when opening the datasource. For detailed permission management, please refer to Dataset Permissions Management.

Name Display Rules

  • The alias format is: server address_database name_Schema name.
  • The dataset name is displayed in the form schema.datasetname (e.g., region.sichuan). The connection symbol can be set to an underscore (e.g., region_sichuan) via SchemaJoin in SuperMap.xml. For specific settings, please refer to Engine-Related Settings.
Note:

If the entered Schema does not exist or the name is incorrect, the datasource can still be opened normally; the system does not validate the Schema name upon opening. However, write operations (such as creating a dataset, importing a dataset) will fail.

Setting Schema When Creating a New Datasource

Setting Instructions

Supports specifying a Schema when creating a new datasource, which is empty by default. If not specified, the system will automatically select a Schema based on the installation status of the PostGIS extension and user permissions.

Specifying a Schema

  • If the PostGIS extension does not exist, the datasource and extension will be created in the specified Schema (if the Schema does not exist, it will be created automatically).

  • If the PostGIS extension already exists:

    • User has creation permissions for the Schema where the extension is located: The datasource is created in that Schema, and the specified Schema is invalid.

    • User only has usage permissions, no creation permissions: The datasource is created in the SDX Schema, and the specified Schema is invalid.

  • If a PostGIS datasource already exists in the target Schema or any datasource exists in SDX, creation will fail.

Not Specifying a Schema

  • If the PostGIS extension exists and the user has creation permissions, the datasource is created in the Schema where the extension is located.

  • If the extension exists but the user has no creation permissions, the datasource is created in the SDX Schema (if it does not exist, it is created automatically).

  • If the PostGIS extension does not exist, the datasource and extension are created in the public Schema.

Compatibility Between Versions

Function Old Version Using Datasource Created by New Version New Version Using Old Version
/ PostGIS Extension and Datasource Not in the Same Schema (and Datasource Schema Name is sdx) PostGIS Extension and System Datasource in the Same Schema PostGIS Extension and System Datasource in the Same Schema
Datasource Opening Opened via direct connection to the original PostGIS datasource, without reading the system table, unable to recognize raster, network, model datasets. Normal Use No Compatibility Issues
Functions Relying on System Tables (e.g., Dataset Creation, Deletion) Cannot Function Properly Normal Use No Compatibility Issues
Edit Data Opened for editing via the original PostGIS datasource; e.g., after CAD editing, the system table is not updated, causing issues with extent and record count maintenance when opened in the new version. System table data consistency may be compromised. Normal Use No Compatibility Issues
Datasource Creation Recognizes existing sdx datasource and will not create a new one. Normal Use No Compatibility Issues
PostgreSQL Opening PostGIS Datasource Can open, but datasets cannot be displayed. Normal Use No Compatibility Issues

Related Topics

New Datasource

Open Datasource