Subject | Error: "no current record for fetch operation" |
---|---|
Author | Andrei Babyuk |
Post date | 2003-06-24T17:07:46Z |
I get this error when running the query below in Firebird 1.5 RC3.
The same query on the same data works fine in Interbase 6.01.
SELECT t2.EE_NBR, t4.CO_NBR, t3.AMOUNT, t4.WORKERS_COMP_WAGE_LIMIT,
t3.RATE_NUMBER, t3.CL_E_DS_NBR, t5.E_D_CODE_TYPE, FROM
Pr_Check_Hist('now') t2, Pr_Check_Lines_Hist('now') t3, Ee_Hist
('now') t4, Cl_E_DS_Hist('now') t5 WHERE t2.PR_CHECK_NBR =
t3.PR_CHECK_NBR AND t5.CL_E_DS_NBR = t3.CL_E_DS_NBR AND t2.PR_NBR = 5
AND t4.EE_NBR = t2.EE_NBR AND t3.PR_NBR = 5 and t5.E_D_CODE_TYPE
LIKE 'E%';
Clearly it has something to do with joined stored procedures, because
if I use real tables instead, the query executes without errors.
Looks like a Firebird bug???
The same query on the same data works fine in Interbase 6.01.
SELECT t2.EE_NBR, t4.CO_NBR, t3.AMOUNT, t4.WORKERS_COMP_WAGE_LIMIT,
t3.RATE_NUMBER, t3.CL_E_DS_NBR, t5.E_D_CODE_TYPE, FROM
Pr_Check_Hist('now') t2, Pr_Check_Lines_Hist('now') t3, Ee_Hist
('now') t4, Cl_E_DS_Hist('now') t5 WHERE t2.PR_CHECK_NBR =
t3.PR_CHECK_NBR AND t5.CL_E_DS_NBR = t3.CL_E_DS_NBR AND t2.PR_NBR = 5
AND t4.EE_NBR = t2.EE_NBR AND t3.PR_NBR = 5 and t5.E_D_CODE_TYPE
LIKE 'E%';
Clearly it has something to do with joined stored procedures, because
if I use real tables instead, the query executes without errors.
Looks like a Firebird bug???