Hi!

> I have created a temp table that deletes all records on commit. (using FB 2.1.4)
>
> My aim is to speed up a report on recipes, where the same item is accessed multiple times for the same report.
>
> So, I am saving that item's stock level in a temporary table, which has made the procedure 10 X faster. (and the fact that all records are deleted as soon as the report is closed is perfect)
>
> But, now that I'm trying to run the stored procedure for the report via my front end, I have the problem that my reports are run in a read only transaction. (so as not to have long running interesting transactions active, as long as that person decides to leave the report/enquiry open on the screen)
>
> Surely, if the table is only visible to MY read-only transaction, I should be allowed to insert records into that temp table, even though the transaction is read-only? (since upon commit, no changes are being made)

http://tracker.firebirdsql.org/browse/CORE-3399

> Otherwise, is there a way of executing a long running query AND updating temp table, WITHOUT creating stuck OIT transactions?
>
> Thanks
> Maya

--
With regards,

Thomas Steinmaurer
Upscene Productions
http://www.upscene.com
http://blog.upscene.com/thomas/

Download LogManager Series, FB TraceManager today!
Continuous Database Monitoring Solutions supporting
Firebird, InterBase, Advantage Database, MS SQL Server
and NexusDB!