Issues to be aware of using Oracle session-based temporal tables

There are two types of temporal tables in Oracle, one based on the session, and the data is emptied when a commit occurs, and the data is emptied when the session is disconnected.

--transaction-based temporal tables

Create global temporary table test
(
ID number
)
on commit delete rows;


--session-based temporal table
Create Global temporary table test
(
ID number
)

on commit preserve rows;

If your system architecture is three times the architecture, there is the concept of connection pooling, such as weblogic+oracle this architecture, in fact, the session will not quit, but after the request is completed, the session will be returned to the connection pool. If you operate a session-based staging table, you do not delete the table after each operation. That data will always accumulate. The best practice is to use the system tests found today in the test environment using the truncate.

Issues to be aware of using Oracle session-based temporal tables