CREATE SCHEMA
Description
Creates a schema.
Named objects are accessed either by "qualifying" their names with the schema name as a prefix, or by setting a search path that includes the desired schema. When creating named objects, you can also use the schema name as a prefix.
Optionally, CREATE SCHEMA can include sub-commands to create objects within the new schema. The sub-commands are treated essentially the same as separate commands issued after creating the schema. If the AUTHORIZATION clause is used, all the created objects are owned by this user.
Precautions
- Only a user with the CREATE permission on the current database can perform this operation.
- The owner of an object created by a system administrator in a schema with the same name as a common user is the common user, not the system administrator.
Syntax
- Create a schema based on a specified name.
1 2
CREATE SCHEMA schema_name [ AUTHORIZATION user_name ] [ schema_element [ ... ] ];
- Create a schema based on a username.
1
CREATE SCHEMA AUTHORIZATION user_name [ schema_element [ ... ] ];
Parameters
- schema_name
Specifies the schema name.
- The schema name must be unique in the current database.
- The schema name cannot be the same as the initial username of the current database.
- The schema name cannot start with pg_.
- The schema name cannot start with gs_role_.
Value range: a string. It must comply with the naming convention.
- AUTHORIZATION user_name
Specifies the owner of a schema. If schema_name is not specified, user_name will be used as the schema name. In this case, user_name can only be a role name.
Value range: an existing username or role name
- schema_element
Specifies an SQL statement defining an object to be created within the schema. Currently, only CREATE TABLE, CREATE VIEW, CREATE INDEX, CREATE PARTITION, and GRANT are supported.
Objects created by sub-commands are owned by the user specified by AUTHORIZATION.
If objects in the schema on the current search path are with the same name, specify the schemas for different objects. You can run SHOW SEARCH_PATH to check the schemas on the current search path.
Examples
1 2 3 4 5 6 7 8 9 10 11 12 13 |
-- Create the role1 role. gaussdb=# CREATE ROLE role1 IDENTIFIED BY '********'; -- Create a schema named role1 for the role1 role. The owner of the films and winners tables created by the clause is role1. gaussdb=# CREATE SCHEMA AUTHORIZATION role1 CREATE TABLE films (title text, release date, awards text[]) CREATE VIEW winners AS SELECT title, release FROM films WHERE awards IS NOT NULL; -- Delete the schema. gaussdb=# DROP SCHEMA role1 CASCADE; -- Delete the user. gaussdb=# DROP USER role1 CASCADE; |
Helpful Links
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot