|
From: Gerd W. <ger...@t-...> - 2023-03-11 02:03:06
|
Am 08.03.23 um 07:33 schrieb Ste...@ha...: > After running a lot of tests I can confirm that the reconnect function does NOT create a 100% identical session > The Initialization String is not used anymore, need to check the code what reconnect is doing because defaultSchema is still the same after reconnect. > This is confusing that only a part of the URL seems to be used. > > jdbc:datadirect:openedge://localhost:12001;databaseName=test;truncateTooLarge=off;defaultSchema=pub;setQueryTimeout=60;InitializationString=(SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED); > Could you please check the following: - Open a new Session - Click the topmost node in the Object tree - Select tab "Status" on the right - What transactionisolationLevel is displayed there? I suspect it is not "TRANSACTION_READ_UNCOMMITTED". If so please contact your JDBC driver vendor and ask him to return the correct isolation level when java.sql.Connection.getTransactionIsolation() is called. Some background information: As long as you don't edit the connection data in the reconnect dialog (see "+"-button) SQuirreL uses exactly the data given in your alias. But there are some properties that SQuirreL restores in a reconnected connection. Those are - Isolation level, which is your concern - Auto commit - Catalog, when applicable all these properties are read using standard JDBC API functions as for example java.sql.Connection.getTransactionIsolation(). Gerd |
