A series of questions from a newbie in firebird-support prompted me to try and reproduce his results. He is trying to chart the effects of READ WRITE READ COMMITTED transactions in two simultaneous isql sessions, with and without WAIT and RECORD_VERSION. His theory was that using SET TRANSACTION in isql would change the attributes of the "default" transaction for the rest of the session. It had never occurred to me that this might be so.
>From my tests, it doesn't seem to be the case. It seems that, as soon as one >commits or rolls back the started transaction, isql starts a new transaction >using the global default (READ WRITE WAIT ISOLATION LEVEL SNAPSHOT). At >least, that is what the tests seem to indicate. Could some isql boffin confirm, or explain? Thanks, Helen ------------------------------------------------------------------------------ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
