Not handled correctly is such a design in Legacy API.
IBExpert
execute block
as
begin
suspend;
end
FB2.5
No result. It's good.
FB3.0
An error was found in the application program input parameters for the SQL
statement.
Incorrect values within SQLDA structure.
SQL error code = -804.
04.05.2014 11:10, Simonov Denis wrote:
execute block
as
begin
suspend;
end
FB2.5
No result. It's good.
IMHO, such construction must produce error no output variables at prepare
time as it
is does select from t:
SQL select from rdb$database;
Statement failed, SQLSTATE = 42000
Dimitry Sibiryakov s...@ibphoenix.com писал(а) в своём письме Sun, 04 May
2014 13:39:22 +0400:
04.05.2014 11:34, Simonov Denis wrote:
Maybe you're right. But I am surprised at the difference in treatment in
the Legacy and the new API. And also the fact that in Fb2.5 is handled
differently.
Sean,
1. A query's operations (the reading of the data and sorting) execute
in a single thread/process, correct?
Correct.
2. Is Internal sorting performed by the ExecuteWriteTempSortBlock()
step?
Internal buffer is sorted as soon as filled up to its limit and then written
into
-Original Message-
From: Thomas Steinmaurer [mailto:t...@iblogmanager.com]
Sent: Domingo, 04 de Mayo de 2014 5:43
Personally, I find it frustrating to what Firebird disk IO
profile when performing large select/sorts, on systems which
have IO to burn (RAM Disk, SSD or PCIe SSD).
Claudio,
-Original Message-
From: Thomas Steinmaurer [mailto:t...@iblogmanager.com]
Sent: Domingo, 04 de Mayo de 2014 5:43
Personally, I find it frustrating to what Firebird disk IO
profile when performing large select/sorts, on systems which
have IO to burn (RAM Disk, SSD or PCIe
