
If you were logged in you would be able to see more operations.
|
|
|
Testing for 2.5, but other versions are also undergone.
isql failed (AV in fbclient.dll) when trying executing select statement, as no fields
exist at that moment. Server should return an error, but doesn't do it.
SET AUTODDL OFF;
SET SQL DIALECT 3;
SET NAMES WIN1251;
CONNECT test25 USER 'SYSDBA' PASSWORD 'masterkey';
CREATE TABLE NEW_TABLE7 (ID SMALLINT NOT NULL);
COMMIT;
insert into NEW_TABLE7(ID) VALUES (0);
COMMIT;
ALTER TABLE NEW_TABLE7
ADD FIELD1 CHAR(1) NOT NULL;
ALTER TABLE NEW_TABLE7
DROP ID;
select * from New_table7;
COMMIT;
--
Best regards, Eugene
|
Description
|
Testing for 2.5, but other versions are also undergone.
isql failed (AV in fbclient.dll) when trying executing select statement, as no fields
exist at that moment. Server should return an error, but doesn't do it.
SET AUTODDL OFF;
SET SQL DIALECT 3;
SET NAMES WIN1251;
CONNECT test25 USER 'SYSDBA' PASSWORD 'masterkey';
CREATE TABLE NEW_TABLE7 (ID SMALLINT NOT NULL);
COMMIT;
insert into NEW_TABLE7(ID) VALUES (0);
COMMIT;
ALTER TABLE NEW_TABLE7
ADD FIELD1 CHAR(1) NOT NULL;
ALTER TABLE NEW_TABLE7
DROP ID;
select * from New_table7;
COMMIT;
--
Best regards, Eugene
|
Show » |
|
So, this issue leaves us with a question: should we allow to fetch records with empty output XSQLDA (sqld == 0) or not? The engine itself is ready for that. Also, some clever person could use this trick to check for EOF (or count rows) without retrieving the values of the select list. Therefore, I tend to fix the code to allow such queries. From another side, this "feature" doesn't make any sense for 99% of the users...
Opinions?