CREATE TABLE POTEST (
POTEST INTEGER,
TKC D_KC12 /* D_KC12 = NUMERIC(15,2) */
);
Po spusteni dotazu:
SELECT DISTINCT r.RDB$FIELD_NAME AS fName,
CASE f.RDB$FIELD_TYPE
WHEN 261 THEN 'BLOB'
WHEN 14 THEN 'CHAR'
WHEN 40 THEN 'CSTRING'
WHEN 11 THEN 'D_FLOAT'
WHEN 27 THEN 'DOUBLE'
WHEN 10 THEN 'FLOAT'
WHEN 16 THEN 'INT64'
WHEN 8 THEN 'INTEGER'
WHEN 9 THEN 'QUAD'
WHEN 7 THEN 'SMALLINT'
WHEN 12 THEN 'DATE'
WHEN 13 THEN 'TIME'
WHEN 35 THEN 'TIMESTAMP'
WHEN 37 THEN 'VARCHAR'
ELSE 'UNKNOWN'
END AS fType,
f.RDB$FIELD_SUB_TYPE AS field_subtype,
f.rdb$dimensions AS dimension
FROM RDB$RELATION_FIELDS r
LEFT JOIN RDB$FIELDS f ON r.RDB$FIELD_SOURCE = f.RDB$FIELD_NAME
WHERE r.RDB$RELATION_NAME='POTEST' -- table name
ORDER BY r.RDB$FIELD_POSITION;
tedy vim ze KC je ciselneho typu, ale potrebuji jeste ktery RDB$ mi
ukaze ze jde o pole, pripadne jeho horni a dolni hranici. To spravne RDB
jsem zatim nenalezl, proto se obracim na konferu.
Dekuji
MaReK Olsavsky
RDB$FIELDS.RDB$DIMENSIONS a RDB$FIELD_DIMENSIONS.*
Ale doporucil bych se polim vyhnout. Je to takovy hack.
--
Jiri {x2} Cincura (x2develop.com founder)
http://blog.cincura.net/ | http://www.ID3renamer.com
MO
Mizerna podpora v SQL a nastrojich. Obecne v relacnim svete divny koncept.
A ve FB to neni uplne first-class koncept (i co se tyka externiho POV,
tak internich veci). Kdyz uz bych to nechtel davat do separatni
tabulky, udelal bych 12 sloupcu, zadna veda.