Module
Contents
Index 🔎︎

# Special Settings

Specifies the way you can work with data in a database.

Jei norite tai atlikti…

In a database window, choose Edit - Database - Advanced Settings

The availability of the following controls depends on the type of database:

## Use SQL92 naming constraints

Only allows characters that conform to the SQL92 naming convention in a name in a data source. All other characters are rejected. Each name must begin with a lowercase letter, an uppercase letter, or an underscore ( _ ). The remaining characters can be ASCII letters, numbers, and underscores.

## Use keyword AS before table alias names

Some databases use the keyword "AS" between a name and its alias, while other databases use a whitespace. Enable this option to insert AS before the alias.

## End text lines with CR + LF

Select to use the CR + LF code pair to end every text line (preferred for DOS and Windows operating systems).

## Append the table alias name in SELECT statements

Appends the alias to the table name in SELECT statements.

## Use Outer Join syntax '{OJ }'

Use escape sequences for outer joins. The syntax for this escape sequence is {oj outer-join}

Example:

select Article.* from {oj item LEFT OUTER JOIN orders ON item.no=orders.ANR}

## Ignore the privileges from the database driver

Ignores access privileges that are provided by the database driver.

## Replace named parameters with ?

Replaces named parameters in a data source with a question mark (?).

## Display version columns (when available)

Some databases assign version numbers to fields to track changes to records. The version number of a field is incremented by one each time the contents of the field are changed. Displays the internal version number of the record in the database table.

## Use the catalog name in SELECT statements

Uses the current data source of the catalog. This option is useful when the ODBC data source is a database server. Do not select this option if the ODBC data source is a dBASE driver.

## Use the schema name in SELECT statements

Allows you to use the schema name in SELECT statements.

## Create index with ASC or DESC statement

Creates an index with ASC or DESC statements.

## Comparison of Boolean values

Select the type of Boolean comparison that you want to use.

## Form data input checks for required fields

When you enter a new record or update an existing record in a form, and you leave a field empty which is bound to a database column which requires input, then you will see a message complaining about the empty field.

If this control box is not enabled, then the forms in the current database will not be checked for required fields.

The control box is available for all data source types which support write access to their data. The control box does not exist for spreadsheets, text, csv, and the various read-only address books.

## Ignore currency field information

Only for Oracle JDBC connections. When enabled it specifies that no column is treated as a currency field. The field type returned from the database driver is discarded.

## Use ODBC conformant date/time literals

Use date/time literals that conform to ODBC standard.

## Supports primary keys

Enable to overrule Base's heuristics used to detect whether the database supports primary keys.

When connecting to a database using a generic API like ODBC, JDBC, or ADO, Base currently applies heuristics to determine whether this database supports primary keys. None of those APIs has dedicated support to retrieve this information.

The heuristics sometimes fails. This tri-state check box by default is set to the undetermined state, which means "apply the heuristics". If the check box is enabled, primary key support is assumed. If the check box is disabled, no primary key support is assumed.

Note that if this option is just for overruling the heuristics. If you enable the check box for a database which actually does not support primary keys, you will see some errors.