Schemas and tables

Schemas

A schema is a namespace inside a database. Every database starts with public, and you can create more to keep unrelated parts of an application from colliding.

Schemas have their own page, and the console lists them under each database in the sidebar so you can move between them without going back to a list.

Creating a schema asks only for a name, which follows PostgreSQL's rules: lowercase letters, numbers and underscores, beginning with a letter.

An app user needs the change the schema capability to create one. See App users.

Tables

Tables can be designed from the console rather than by writing DDL by hand. The designer collects the columns, their types and whether each one accepts nulls, and produces the CREATE TABLE it is going to run.

You are shown that statement before it runs. Reviewing generated DDL is the difference between understanding your schema and hoping.

Anything the designer cannot express is still available: open Querying and write the statement yourself. The designer is a convenience for the common shape, not a restriction on what your database may contain.

Browsing what is there

Each schema lists its tables and views, and each table shows its columns and their types. This is read from the database itself rather than from a record HiveOps keeps, so it reflects whatever is actually there, including objects created outside the console.