External table data not visible to other sessions in Classic [CORE2475] #2888
Submitted by: Tim Barber (tim.barber)
In 2.1.2 SuperServer, any data written to external tables are visible to other sessions.
Super Server behaviour:
====== Test Details ======
THIS TEST WILL END WITH ERROR IF EXTERNAL TABLE ACCESS IS NOT ALLOWED, WHICH IS BY DEFAULT.
The text was updated successfully, but these errors were encountered:
Commented by: Tim Barber (tim.barber)
I agree that import/export would be one of the main uses of external tables, but they are defined as being like tables with certain restrictions - inter-session data visibility not being one of them.
We started development of a project that utilises external tables using Firebird 2.0 and have started testing against Firebird 2.1.2 where we discovered this issue - Firebird 2.0 behaves as expected (besides the locking problems that is!).
Looks like other Firebird users expect this behaviour:
Commented by: @hvlad
Before v2.1 external table's IO was performed without caching and thus was very slow.
Modified by: @pavel-zotov
status: Closed [ 6 ] => Closed [ 6 ]
QA Status: Done successfully
Test Details: THIS TEST WILL END WITH ERROR IF EXTERNAL TABLE ACCESS IS NOT ALLOWED, WHICH IS BY DEFAULT.
Test Specifics: [Custom configuration required]