Nickname column and index names

When you create a nickname, the federated server uses an algorithm to generate nickname column and index names.

This algorithm is enhanced in Version 9.5 to match the nickname column and index names and the original names as closely as possible.

The algorithm applies only to relational data sources. For non-relational data sources, the name specified in the CREATE NICKNAME statement remains unchanged.

The following table shows examples of nickname column names that result from remote column names. In these examples, the remote columns are in separate remote tables. The nickname column names that differ from the remote column name are shown in bold.
Table 1. Nickname column names generated from remote column names.
Remote column name Name that results from current algorithm for data sources that .. Name that resulted before Version 9.5 (algorithm folds and converts non-alphanumeric characters)
Fold identifiers to upper case Fold identifiers to lower case Leave identifiers unchanged
column1 column1 COLUMN1 COLUMN1 COLUMN1
Column1 Column1 Column1 COLUMN1 COLUMN1
COLUMN1 COLUMN1 COLUMN1 COLUMN1 COLUMN1
column-1 column-1 column-1 column-1 COLUMN_1
Column-1 Column-1 Column-1 Column-1 COLUMN_1
COLUMN-1 COLUMN-1 COLUMN-1 COLUMN-1 COLUMN_1
If the remote columns are in the same table, the federated server uses the existing algorithm that generates unique names. For example, for the nickname column names for the data sources that leaves identifiers unchanged, the remote column names result in the following names:
  • column1 results in COLUMN1
  • Column1 results in COLUMN10
  • COLUMN1 results in COLUMN11