You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The function "void IscConnection::parseReservingTable( ... )" did not work like it should. It is used to parse a "set transaction" command and check if some tables are required to be used in a special reservation mode.
it is possible to define several tables in a comma separated list for a special reserving mode. The function does not respect this possibility. Only the comma for separation of different "<table_spec>" clauses is respected.
Furthermore there seems to be a problem in setting the "lockMode" for the table. Within the last "if" section for all tables found during the parsing, the "lockMode" of the last "<table_spec>" clause is set. So the possibility of having different "lockMode" for each "<table_spec>" clause is not respected.
Submitted by: Marco Held (demig-mh)
Assigned to: @samofatov
The function "void IscConnection::parseReservingTable( ... )" did not work like it should. It is used to parse a "set transaction" command and check if some tables are required to be used in a special reservation mode.
According to the sql syntax declaration
SET TRANSACTION
[NAME hostvar]
[READ WRITE | READ ONLY]
[ [ISOLATION LEVEL] { SNAPSHOT [TABLE STABILITY]
| READ COMMITTED [[NO] RECORD_VERSION] } ]
[WAIT | NO WAIT]
[LOCK TIMEOUT seconds]
[NO AUTO UNDO]
[IGNORE LIMBO]
[RESERVING <tables> | USING <dbhandles>]
<tables> ::= <table_spec> [, <table_spec> ...]
<table_spec> ::= tablename [, tablename ...]
[FOR [SHARED | PROTECTED] {READ | WRITE}]
<dbhandles> ::= dbhandle [, dbhandle ...]
it is possible to define several tables in a comma separated list for a special reserving mode. The function does not respect this possibility. Only the comma for separation of different "<table_spec>" clauses is respected.
Furthermore there seems to be a problem in setting the "lockMode" for the table. Within the last "if" section for all tables found during the parsing, the "lockMode" of the last "<table_spec>" clause is set. So the possibility of having different "lockMode" for each "<table_spec>" clause is not respected.
Commits: 39ba753 bc3f5c1
The text was updated successfully, but these errors were encountered: