DB Query Reader with Database Transaction

Hi all,

yet another question regarding the usage of DB Transaction nodes.

My workflow looks roughly like this:

The first 4 nodes within the transaction do some typical delete-insert-update stuff which is necessary to be handled within one transaction. So far so good.

At the end of this, I need to do a SELECT (for which I use the DB Query Reader node) to get the data into KNIME. Only then, the transaction shall be committed, because the SELECT must see everything that happened in the transaction before, and all of this must be atomic.

Question: In this construct, is the DB Query Reader node really part of the transaction? If not, how can I make it part of the transaction? What state does it see when executed?

The ambiguous part is obviously that the DB Query Reader has no DB Session out-port that I could connect to the Transaction End node. Why?