Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CREATE VIEW issues "Implementation of text subtype 512 not located" [CORE5846] #6107

Closed
firebird-automations opened this issue Jun 18, 2018 · 4 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @pavel-zotov

Adjust folder+name of database and run script:

shell del C:\MIX\firebird\QA\fbt-repo\tmp\c5448.fdb 2>nul;
set bail on;
set echo on;
create database 'localhost:C:\MIX\firebird\QA\fbt-repo\tmp\c5448.fdb' default character set utf8;

alter character set utf8 set default collation unicode;
create table table1( fld1 char(1) character set none );
create view view1 as
select fld1 from table1
;

Last statement ('create view ...') will issue on WI-V3.0.4.32988 and WI-T4.0.0.1008:

Statement failed, SQLSTATE = 42000
unsuccessful metadata update
-VIEW1
-Implementation of text subtype 512 not located.

No such error on WI-V2.5.9.27111

PS.
Vlad suggested me to create separate ticket for this bug; initial message about it see in CORE5448, 02/Feb/17 11:36 AM.

Commits: f1413be da61869 1a29188 83c227d

@firebird-automations
Copy link
Collaborator Author

Modified by: @asfernandes

assignee: Adriano dos Santos Fernandes [ asfernandes ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @asfernandes

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 4.0 Beta 1 [ 10750 ]

Fix Version: 3.0.4 [ 10863 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

status: Resolved [ 5 ] => Resolved [ 5 ]

QA Status: No test => Done successfully

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

status: Resolved [ 5 ] => Closed [ 6 ]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment