You’re offline. This is a read only version of the page.
17,788
Just curious if anyone else has noticed this.
We're using a TempDB temporary table joined 1:1 on the ProdRouteOprOverviewListPage and ProdRouteOprOverview forms against ProdTable. I suspect that the temporary table joined as a child might be a factor. In the form .init() method we insert records into the TempDB table once, so that subsequent executeQuery() will continue to work against this one-time set of data (not refreshed each time the data source is refreshed).
The problem is that when either form closes, and the "variable" sustaining the TempDB tables goes out of scope (presumably because the data source itself does), the TempDB table is not removed. As a result, our TempDB database grows gradually over time, littered with these t107262_etc tables until we restart the AOS (which closes all of the active connections and effectively all of the TempDB tables sustained by those connections). I'm resorting to doing a delete_from on my TempDB table in the form .close() method, but it seems like a problem with the product to allow the TempDB to fill in this way.
Anyone seen anything similar?
The version is R2 no CU. Not yet tested in R3 or R3 CU8.
*This post is locked for comments
I have the same question (0)
So, while I'd like to do a delete_from on the joined temporary table when the hosting form closes, from a List page this appears impossible. How do we intercept the .close() event on a List page? We certainly can't override the .close() method on the List page itself, and I can find no examples or documentation on whether such a method exists on the ListPageInteraction class. Ideas?
Share
Report
All responses (
Answers (
