DML statements executed from the Editor get auto-committed? Data changes reflected in different t (4228380)

Are DML statements getting auto-committed? Data changes are reflected in different tabs and windows in a Toad session, but "Apply commit/rollback to all
tabs (threaded queries)" is unchecked in the TOAD options and commit is never run. If in a new Toad session, the data changes are not reflected?

How can you view data in the database, in different tabs and windows in Toad, without seeing the changes that might have been applied but not committed?


Example:
1. Insert into tab1 (col1,col2) values (1,2); Execute this statement in one tab in the Editor.
2. Run select * from tab1 after running the insert (no commit). This should return the newly inserted rows in the grid.
3. Now open a separate tab inside the same Editor and run select * from tab1.

Ideally, it wouldn't return the last row that was just inserted. You wouldn't see the newly inserted record in the Data tab of the table in the Schema Browser, either. But currently, the Editor behaves differently and now the DML statement and data changes are reflected in other tabs/windows throughout Toad, even though the auto commit feature is disabled, and not commit is manually run, nor any command followed by an implement commit.

"Execute Queries in Threads (create separate sessions)" setting determines what session each tab/window is associated to, which determines what changes will be reflected or not.

Having this option unchecked/disabled will run all on one session and reflect changes in all windows/tabs

View | Toad options | Oracle | Transactions, and check "Execute Queries in Threads (create separated sessions)".

Enabling this will associate the different windows/tabs to different sessions, so that non committed dml changes are not reflected across.