If some VIEW used derived tables and long table names\aliases, It is possible to overflow RDB$VIEW_RELATIONS.RDB$CONTEXT_NAME [CORE1841] #2270
Labels
affect-version: 2.0.0
affect-version: 2.0.1
affect-version: 2.0.2
affect-version: 2.0.3
affect-version: 2.1 Alpha 1
affect-version: 2.1 Beta 1
affect-version: 2.1 Beta 2
affect-version: 2.1 RC1
affect-version: 2.1 RC2
affect-version: 2.5 Initial
component: engine
fix-version: 2.0.5
fix-version: 2.1.1
fix-version: 2.5 Alpha 1
priority: major
qa: done successfully
type: bug
Submitted by: @hvlad
Is related to QA215
In RDB$VIEW_RELATIONS.RDB$CONTEXT_NAME stored full table alias - concatenation of all outer derived table's names and this table name.
As RDB$CONTEXT_NAME declared as CHAR(31) it is very easy to oferflow it.
In this case such VIEW can't be created.
Example :
create view x (id) as
select RDB$RELATION_ID
from (select * from RDB$DATABASE long_alias_long_alias_1) long_alias_long_alias_2
This operation is not defined for system tables.
unsuccessful metadata update.
Name longer than database column size.
Commits: dcd7f80 512e626 6ee4242
The text was updated successfully, but these errors were encountered: