Metadata tables defining jobs and the related OLAP objects
Because of potential issues with joins in views, we recommend that you use tables and not views for relational loads from PostgreSQL sources. In PostgreSQL, column names are case-sensitive. We recommend that you always use quotes in requests for table and column names. Unquoted table and column names are rendered in lowercase.
Keep these points in mind:
- The SQL syntax used is for SQL Server and Amazon Redshift. PostgreSQL is also handled. The syntax for PostgreSQL is the same as for SQL Server.
- Amazon Redshift is supported as a data source for dimension member tables and fact tables. Amazon Redshift is not supported for metadata tables.
- A comment column is present in every metadata table. It is not processed by the server. You can use it to add notes relating to the rows they refer to. Although this column appears in each CREATE TABLE command, it is not referred to in the table descriptions.
- Element names can only have string values.
- Table names defined by the user cannot contain spaces or reserved words. They can be sub-queries.
- Optionally, table names that are not sub-queries can be escaped.
- Sub-queries used in place of tables must not be escaped.
- Do not use white space characters in sub-queries other than the standard space character " ". For example, do not use tabs or carriage returns.
- Do not use an alias with a table name.
- The portion of a sub-query preceding any alias must be placed between parentheses "(" and ")". This means the whole query if no alias is present.
Though you can use tables or views, the documentation refers to tables for simplification purposes.