18.02.2019 13:19, Adriano dos Santos Fernandes wrote:
On 18/02/2019 05:50, Vlad Khorsun wrote:
18.02.2019 1:49, Adriano dos Santos Fernandes wrote:
Open two connections C1 and C2.
C2: select current_transaction from rdb$database; -- let's call the
result T2
C2: commit;
C1: select rdb$get_transaction_cn(T2) from rdb$database;
In Super C1 returns the commit number. In Classic it returns NULL.
Yes, this is because C1 see no new Next value and consider T2 as not
existing.
We could refresh TIP Cache in C1 but it looks as overkill in this case.
That difference is not documented.
README.builtin_functions.txt:
---
Summary, numbers returned by RDB$GET_TRANSACTION_CN could have values
below:
...
NULL - given transaction number is NULL or greater than database Next
Transaction
---
Considering that (and not), was is
the usefulness of RDB$GET_TRANSACTION_CN?
It is completely useless, if you wish to say it ;)
Seriously, if you (and others) consider it is important enough to try to
refresh
TIP cache in such cases - fill the ticket in tracker and i'll fix it.
Regards,
Vlad
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
