Этот баннер — требование Роскомнадзора для исполнения 152 ФЗ.
«На сайте осуществляется обработка файлов cookie, необходимых для работы сайта, а также для анализа использования сайта и улучшения предоставляемых сервисов с использованием метрической программы Яндекс.Метрика. Продолжая использовать сайт, вы даёте согласие с использованием данных технологий».
Политика конфиденциальности
|
|
|
Создание NickName
|
|||
|---|---|---|---|
|
#18+
Привет всем! При создании NickName на таблицу, которая содержит столбец типа long varchar, выдается сообщение "Столбец типа 'longvar' неизвестен". (DB2 7.2) Заранее спасибо. ... |
|||
|
:
Нравится:
Не нравится:
|
|||
| 12.10.2006, 19:15 |
|
||
|
Создание NickName
|
|||
|---|---|---|---|
|
#18+
7 версия снята с поддержки 1.5 года назад. ... |
|||
|
:
Нравится:
Не нравится:
|
|||
| 12.10.2006, 19:21 |
|
||
|
Создание NickName
|
|||
|---|---|---|---|
|
#18+
на long varchar сплошь и рядом ограничения, смотрите "DB2 SQL Reference Version 7" читаем : CREATE NICKNAME The federated server does not support those data source data types that correspond to the following DB2 data types: LONG VARCHAR , LONG VARGRAPHIC, DATALINK, large object (LOB) types, and user-defined types. When a nickname is defined for a data source table or view, only those columns in the table or view that have supported data types will be defined to, and can be queried from, the federated database. When the CREATE NICKNAME statement is run against a table or view that has columns with unsupported data types, an error is issued. Because data types might be incompatible between data sources, the federated server makes minor adjustments to store remote catalog data locally as needed. Refer to the Application Development Guide for details. The maximum allowable length of DB2 index names is 18 characters. If a nickname is being created for a table that has an index whose name exceeds this length, the entire name is not cataloged. Rather, DB2 truncates it to 18 characters. If the string formed by these characters is not unique within the schema to which the index belongs, DB2 attempts to make it unique by replacing the last character with 0. If the result is still not unique, DB2 changes the last character to 1. DB2 repeats this process with numbers 2 through 9, and if necessary, with numbers 0 through 9 for the name’s seventeenth character, sixteenth character, and so on, until a unique name is generated. To illustrate: The index of a data source table is named ABCDEFGHIJKLMNOPQRSTUVWXYZ. The names ABCDEFGHIJKLMNOPQR and ABCDEFGHIJKLMNOPQ0 already exist in the schema to which this index belongs. The new name is over 18 characters; therefore, DB2 truncates it to ABCDEFGHIJKLMNOPQR. Because this name already exists in the schema, DB2 changes the truncated version to ABCDEFGHIJKLMNOPQ0. Because this latter name exists, too, DB2 changes the truncated version to ABCDEFGHIJKLMNOPQ1. This name does not already exist in the schema, so DB2 now accepts it as a new name. When a nickname is created for a table or view, DB2 stores the names of the table’s or view’s columns in the catalog. If a name exceeds the maximum allowable length for DB2 column names (30 characters), DB2 truncates the name to this length. If the truncated version is not unique among the other names of the table’s or view’s columns, DB2 makes it unique by following the procedure described in the preceding paragraph. ... |
|||
|
:
Нравится:
Не нравится:
|
|||
| 13.10.2006, 09:47 |
|
||
|
|

start [/forum/topic.php?fid=43&msg=34051892&tid=1605071]: |
0ms |
get settings: |
8ms |
get forum list: |
14ms |
check forum access: |
3ms |
check topic access: |
3ms |
track hit: |
59ms |
get topic data: |
10ms |
get forum data: |
2ms |
get page messages: |
48ms |
get tp. blocked users: |
2ms |
| others: | 224ms |
| total: | 373ms |

| 0 / 0 |
