Fujitsu UDS/SQL V2.5 用户手册
SSL
Linkage methods
U929-J-Z125-9-76
149
D
ok
us
c
h
abl
on
en
1
9x
24 V
e
rs
ion
7
.3
us
f
ü
r F
ram
eM
ak
er
V
7
.x
v
o
m
1
4.
02
.2
00
7
©
c
o
gni
tas
Gm
b
H
20
01-
20
07
24
. Ok
tobe
r 20
07
S
ta
nd
0
8:
58
.5
5
P
fa
d:
G
:\
v
og
t\
fs
c
\ud
s
\M
anu
al
e
\e
n\
ud
s
e
nt
_e\
u
ds
ent
.k
0
5
The physical placement of records can be defined only once:
–
If a record type is a member of several sets, only one of the sets can be defined with
MODE IS LIST.
MODE IS LIST.
–
It is not possible to define records with MODE IS LIST and PLACEMENT
OPTIMIZATION at the same time (see the section
OPTIMIZATION at the same time (see the section
).
–
If the records of a record type are placed both by LOCATION MODE IS CALC and
MODE IS LIST, they are stored in lists, and the hash area consists of indirect CALC
pages.
MODE IS LIST, they are stored in lists, and the hash area consists of indirect CALC
pages.
The following restrictions also apply:
MODE IS LIST may only be specified if the set membership has been defined as
MANDATORY AUTOMATIC in the schema DDL (see the section
MANDATORY AUTOMATIC in the schema DDL (see the section
).
MODE IS LIST may not be specified in the following cases:
–
, SCD) exceed
–
993 bytes in a database with a 2048-byte page length (2-Kbyte page format)
–
1963 bytes in a database with a 4000-byte page length (4-Kbyte page format)
–
4011 bytes in a database with a 8096-byte page length (8-Kbyte page format)
(At least two records must fit in a list, but this would not be possible in the above cases.)
–
if a member record type contains an item of variable length;
–
if the order of the records within the set occurrence is defined with ORDER IS SORTED
(without INDEXED) or
(without INDEXED) or
–
if member records are to be stored in compressed form (see the section
).