solicharter.blogg.se - Curly brackets sql

#Curly brackets sql code
#Curly brackets sql series

#Curly brackets sql code

The default country code is US English 1. If this specification is omitted, the LOB pages use the default page size. All LOBs will use pages of this size for storing LOBs, unless the LOB fits into the data page. You should specify this only once, even if the table has multiple LOB columns. It is required only if one or more columns in the table contain LOB characters. The LOB PAGESIZE identifies the number of digits, KB, or MB reserved for the CLOB or BLOB index. If both table and LOB pagesizes are specified, either the table or the LOB pagesize can be defined before the other. If this specification is omitted, the LOB uses the default pagesize. Use the LOB PAGESIZE keywords after all the column definitions and table constraint definitions to define the page size of the BLOB and CLOB columns. If this option is NOT used, char, varchar, and CLOB columns use US ASCII values. When this option is used, char data is stored as Unicode. This is useful if you wish to execute any stored procedures within the transaction, after you executed the CREATE SCHEMA statement. After the commit or rollback, the path will revert to the current_path value that existed prior to the CREATE SCHEMA statement. With this parameter, you can set a default path that will remain as the default until a commit or rollback occurs. This specifies a list of schema_names to access when resolving unqualified. If user_name is not specified the current user_name is the owner of the schema. User_name must exist in the database or an error is raised. Use the following DDL statements and operations to begin building your PointBase database. The Data Definition Language (DDL) is essential to creating a database. The following section describes the syntax for creating and managing logical data objects.

#Curly brackets sql series

Ellipses in an SQL statement have the same meaning as "etc." they denote that the series of keywords, clauses, or variables that precede the ellipses go on indefinitely.

Ellipses are sets of periods (such as ".").

Curly braces in SQL statements indicate that one or more clauses are used together.

If an optional clause has several components or keywords, they display within the brackets.

The clauses in an SQL statement that display between are optional.

The values for variables in conditional expressions are case sensitive. SQL values used in PointBase SQL can be constants, column names, values formed from combinations of column values and constants, or the result of any function that returns a single value.

Portions of SQL statements that display in lowercase italic are SQL values.

Keywords are not case sensitive, and they must be spelled exactly as they display in this document.

If a portion of an SQL statement displays in UPPERCASE, the capitalized words are keywords, which are generally required in the SQL statement or clause.

Some clauses may include a more detailed explanation of their own syntax or links to other documents that describe clauses that are common to more than one SQL statement.Įach SQL statement uses certain types of capitalization, formatting, and punctuation that describe the attributes of different portions of the statement.

Detailed explanations are then described for each keyword and clause in the statement.

Immediately following the statement syntax is a brief description of the overall statement.

The statement syntax follows the conventions described in "Syntax Conventions," below.

The statement keyword(s) is followed by the syntax of the statement.

Each statement page starts with the primary keyword of the statement, which displays at the heading of the page for example, SELECT.Syntax conventions convey specific information about keywords and clauses in the SQL statements described in this document.Įach SQL statement in the data manipulation language, data definition language, and transaction control sections of the PointBase SQL documentation uses a specific page format.Page format conventions provide a structure for the organization of individual pages in the documentation.This section describes documentation conventions.