GSETTINGS(1) User Commands GSETTINGS(1)NAME
gsettings - GSettings configuration tool
gsettings get SCHEMA [:PATH] KEY
gsettings monitor SCHEMA [:PATH] [KEY]
gsettings writable SCHEMA [:PATH] KEY
gsettings range SCHEMA [:PATH] KEY
gsettings set SCHEMA [:PATH] KEY VALUE
gsettings reset SCHEMA [:PATH] KEY
gsettings reset-recursively SCHEMA [:PATH]
gsettings list-keys SCHEMA [:PATH]
gsettings list-children SCHEMA [:PATH]
gsettings list-recursively [SCHEMA [:PATH]]
gsettings help [COMMAND]
gsettings offers a simple commandline interface to GSettings. It lets you get, set or monitor an individual key for changes.
The SCHEMA and KEY arguments are required for most commands to specify the schema id and the name of the key to operate on. The schema id
may optionally have a :PATH suffix. Specifying the path is only needed if the schema does not have a fixed path.
When setting a key, you also need specify a VALUE The format for the value is that of a serialized GVariant, so e.g. a string must include
explicit quotes: "'foo'". This format is also used when printing out values.
Gets the value of KEY. The value is printed out as a serialised GVariant.
Monitors KEY for changes and prints the changed values. If no KEY is specified, all keys in the schema are monitored. Monitoring will
continue until the process is terminated.
Finds out whether KEY is writable.
Queries the range of valid values for KEY.
Sets the value of KEY to VALUE. The value is specified as a serialised GVariant.
Resets KEY to its default value.
Reset all keys under the given SCHEMA.
Lists the installed, non-relocatable schemas. See list-relocatable-schemas if you are interested in relocatable schemas.
Lists the installed, relocatable schemas. See list-schemas if you are interested in non-relocatable schemas.
Lists the keys in SCHEMA.
Lists the children of SCHEMA.
Lists keys and values, recursively. If no SCHEMA is given, list keys in all schemas.
Prints help and exits.
Check Out this Related Man Page
CREATE SCHEMA(7) SQL Commands CREATE SCHEMA(7)NAME
CREATE SCHEMA - define a new schema
CREATE SCHEMA schemaname [ AUTHORIZATION username ] [ schema_element [ ... ] ]
CREATE SCHEMA AUTHORIZATION username [ schema_element [ ... ] ]
CREATE SCHEMA enters a new schema into the current database. The schema name must be distinct from the name of any existing schema in the
A schema is essentially a namespace: it contains named objects (tables, data types, functions, and operators) whose names can duplicate
those of other objects existing in other schemas. 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(s). A CREATE command specifying an unqualified object name creates the
object in the current schema (the one at the front of the search path, which can be determined with the function current_schema).
Optionally, CREATE SCHEMA can include subcommands to create objects within the new schema. The subcommands are treated essentially the same
as separate commands issued after creating the schema, except that if the AUTHORIZATION clause is used, all the created objects will be
owned by that user.
The name of a schema to be created. If this is omitted, the user name is used as the schema name. The name cannot begin with pg_, as
such names are reserved for system schemas.
The name of the user who will own the schema. If omitted, defaults to the user executing the command. Only superusers can create
schemas owned by users other than themselves.
An SQL statement defining an object to be created within the schema. Currently, only CREATE TABLE, CREATE VIEW, CREATE INDEX, CREATE
SEQUENCE, CREATE TRIGGER and GRANT are accepted as clauses within CREATE SCHEMA. Other kinds of objects may be created in separate
commands after the schema is created.
To create a schema, the invoking user must have the CREATE privilege for the current database. (Of course, superusers bypass this check.)
Create a schema:
CREATE SCHEMA myschema;
Create a schema for user joe; the schema will also be named joe:
CREATE SCHEMA AUTHORIZATION joe;
Create a schema and create a table and view within it:
CREATE SCHEMA hollywood
CREATE TABLE films (title text, release date, awards text)
CREATE VIEW winners AS
SELECT title, release FROM films WHERE awards IS NOT NULL;
Notice that the individual subcommands do not end with semicolons.
The following is an equivalent way of accomplishing the same result:
CREATE SCHEMA hollywood;
CREATE TABLE hollywood.films (title text, release date, awards text);
CREATE VIEW hollywood.winners AS
SELECT title, release FROM hollywood.films WHERE awards IS NOT NULL;
The SQL standard allows a DEFAULT CHARACTER SET clause in CREATE SCHEMA, as well as more subcommand types than are presently accepted by
The SQL standard specifies that the subcommands in CREATE SCHEMA can appear in any order. The present PostgreSQL implementation does not
handle all cases of forward references in subcommands; it might sometimes be necessary to reorder the subcommands in order to avoid forward
According to the SQL standard, the owner of a schema always owns all objects within it. PostgreSQL allows schemas to contain objects owned
by users other than the schema owner. This can happen only if the schema owner grants the CREATE privilege on his schema to someone else.
ALTER SCHEMA [alter_schema(7)], DROP SCHEMA [drop_schema(7)]
SQL - Language Statements 2010-05-14 CREATE SCHEMA(7)