Class annotations

Tagged values

The tagged values specific to Sybase possible at class level are presented in the following table:

The ... tagged value	is used to ...	Sybase
{primaryKey}	define the primary key of the class and create an index with direct access.	PRIMARY KEY
{key}	declare a key on a combination of attributes.	UNIQUE
{index}	specify an index on a combination of attributes.	CREATE INDEX
{check}	declare a "check" type constraint on a combination of attributes.	CHECK
{fillfactor}	specify the percentage of pages filled by the index	WITH FILLFACTOR
{tablespace}	specify the name of the segment in which the table will be allocated.	ON
{partition}	specify the number of pages chained together in the table.	PARTITION
{maxRowsPerPage}	specify the maximum number of tuples per page	WITH MAX_ROWS_ PER_PAGE

The {key} tagged value

This {key} tagged value is used to define uniqueness constraints associated with the generated table. The descriptor gives the name, whilst the parameters provide the necessary columns.

The {check} tagged value

The {check} tagged value allows the specification of a Boolean expression in a combination of columns of the table, that will have to be checked so that a tuple be inserted in the table.

This tagged value has for unique parameter the logical condition, used as is, for building the clause's SQL. We recommend that you place this parameter between inverted commas for the syntactical analyzer.

Example:

{check}("(att1 + att2) between 1 and 12")

Note: Remember in this case that if you wish to incorporate the " character in a tagged value's parameter, you must enter the ~ character before it.

The {fillfactor} tagged value

This tagged value specifies the fill factor of each index page. The {fillfactor} must be between 1 and 100.

If the {fillfactor} is not specified, the default value is 0.

A 0 {fillfactor} creates indexes clustered with full pages and indexes not clustered by full page sheets.

Note: Please see Sybase SQL Server Reference Manual Vol 1 pages 3-79).

The {partition} tagged value

This tagged value specifies the number of chain pages in the table. It allows the SQL to execute insertions at the same time on the last page of each chain.

The partition must be greater than or equal to 2. By default, there is only one chain of pages per table.

Note: Please refer to Sybase SQL Server Reference Manual Vol 1 pages 3-15).

The {maxRowsPerPage} tagged value

This tagged value allows the specification of the maximum number of tuples per page in the table.

{maxRowsPerPage} must be between 0 and 256.

If the {maxRowsPerPage} is not specified, the default value is 0.

A 0 value for {maxRowsPerPage} creates indexes that are clustered with full pages and indexes not clustered by full page sheets.

Note: Please refer to Sybase SQL Server Reference Manual Vol 1 pages 3-80.

The {tablespace} tagged value

This tagged value specifies a specific segment of allocation of the table's pages.

The segment will have to have been created first by the administrator using the sp_addsegment procedure.

The {schemaBD} tagged value

The {schemaBD} tagged value has no impact on the Sybase coupling.