
If you were logged in you would be able to see more operations.
|
|
|
Environment:
|
Windows, Linux, Delphi, PHP
|
|
Please run the following SQL and you will notice that the computed by field has a difference in the RDB$FIELD_SUB_TYPE & RDB$FIELD_PRECISION columns. Surely the computed field should inherit the properties of the fields it is using for its calculation.
create table example (
field1 numeric (10,2) default 0,
field2 numeric (10,2) default 0,
total computed by (field1 + field2)
);
commit;
SELECT a.RDB$RELATION_NAME, a.RDB$FIELD_NAME, b. RDB$FIELD_LENGTH, b.RDB$FIELD_SCALE, c.RDB$TYPE_NAME, b.RDB$FIELD_TYPE, b.RDB$FIELD_SUB_TYPE, b.RDB$FIELD_PRECISION, b.RDB$COMPUTED_SOURCE
FROM RDB$RELATION_FIELDS a JOIN RDB$FIELDS b ON (b.RDB$FIELD_NAME = a.RDB$FIELD_SOURCE)
LEFT JOIN RDB$TYPES c ON (b.RDB$FIELD_TYPE = c.RDB$TYPE and c.RDB$FIELD_NAME = 'RDB$FIELD_TYPE')
WHERE a.RDB$RELATION_NAME = 'EXAMPLE' ORDER BY a.RDB$RELATION_NAME, a.RDB$FIELD_POSITION
|
Description
|
Please run the following SQL and you will notice that the computed by field has a difference in the RDB$FIELD_SUB_TYPE & RDB$FIELD_PRECISION columns. Surely the computed field should inherit the properties of the fields it is using for its calculation.
create table example (
field1 numeric (10,2) default 0,
field2 numeric (10,2) default 0,
total computed by (field1 + field2)
);
commit;
SELECT a.RDB$RELATION_NAME, a.RDB$FIELD_NAME, b. RDB$FIELD_LENGTH, b.RDB$FIELD_SCALE, c.RDB$TYPE_NAME, b.RDB$FIELD_TYPE, b.RDB$FIELD_SUB_TYPE, b.RDB$FIELD_PRECISION, b.RDB$COMPUTED_SOURCE
FROM RDB$RELATION_FIELDS a JOIN RDB$FIELDS b ON (b.RDB$FIELD_NAME = a.RDB$FIELD_SOURCE)
LEFT JOIN RDB$TYPES c ON (b.RDB$FIELD_TYPE = c.RDB$TYPE and c.RDB$FIELD_NAME = 'RDB$FIELD_TYPE')
WHERE a.RDB$RELATION_NAME = 'EXAMPLE' ORDER BY a.RDB$RELATION_NAME, a.RDB$FIELD_POSITION
|
Show » |
There are no subversion log entries for this issue yet.
|
|