description: SFID: 1260233#⁠
Submitted By: agjedrus

I would vote for Materialized Views, that will help to
implement caching mechanizm for complicated reports.
Result of the timeconsuming query could be stored in
such view with some generated at runtime name, for
later usage eg. paging, sorting.... For sure such
snapshot has to be very fast lets say 100.000 (ID,
ROWNUM) < 1s

Implementation of such query persistency could be
more or lest like in Oracle.
I wanted to use in such purpose External File Table, but
table generated by EXECUTE STATEMENT is not visible
inside stored procedure that has created it. Another
workaround with "normal table" with sessionid is very
slow, inserting and deleting is timeconsuming.

=>

SFID: 1260233#⁠
Submitted By: agjedrus

I would vote for Materialized Views, that will help to
implement caching mechanizm for complicated reports.
Result of the timeconsuming query could be stored in
such view with some generated at runtime name, for
later usage eg. paging, sorting.... For sure such
snapshot has to be very fast lets say 100.000 (ID,
ROWNUM) < 1s

Implementation of such query persistency could be
more or lest like in Oracle.
I wanted to use in such purpose External File Table, but
table generated by EXECUTE STATEMENT is not visible
inside stored procedure that has created it. Another
workaround with "normal table" with sessionid is very
slow, inserting and deleting is timeconsuming.

Workflow: jira [ 10846 ] => Firebird [ 15286 ]

Link: This issue is duplicated by CORE2336 [ CORE2336 ]