When you use calculated fields in a view, whether the field type is cast to a domain through the Cast function, whether it is a known domain from the result of a stored procedure or function, or simply derived dynamically from an expression, in any case, the automatically generated RDB$<number> domain is used to create the view for that field.
Please improve the functionality so that when creating a view, the domains available in the database are taken into account for the calculated fields, if, based on the expression, the domain is known (when the end result is brought to a specific domain via Cast or is a known domain from the result of a stored procedure or function), so that when creating views with such fields, the automatically created RDB$<number>domains do not multiply.
firebird-automations
commented
5 years ago
Submitted by: rdb_dev (rdb_dev)
Votes: 2
When you use calculated fields in a view, whether the field type is cast to a domain through the Cast function, whether it is a known domain from the result of a stored procedure or function, or simply derived dynamically from an expression, in any case, the automatically generated RDB$<number> domain is used to create the view for that field.
Please improve the functionality so that when creating a view, the domains available in the database are taken into account for the calculated fields, if, based on the expression, the domain is known (when the end result is brought to a specific domain via Cast or is a known domain from the result of a stored procedure or function), so that when creating views with such fields, the automatically created RDB$<number>domains do not multiply.