New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
External table data not visible to other sessions in Classic [CORE2475] #2888
Comments
Commented by: Sean Leyne (seanleyne) An external table feature was not intended for inter-session data transfer, but rather simple text import/export functionality. IMHO, this is as-designed functionality. |
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: |
Modified by: @hvladassignee: Vlad Khorsun [ hvlad ] |
Commented by: @hvlad Before v2.1 external table's IO was performed without caching and thus was very slow. |
Modified by: @hvladstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.5 RC1 [ 10300 ] |
Commented by: @hvlad Backported into 2.1.3 |
Modified by: @hvladFix Version: 2.1.3 [ 10302 ] |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Commented by: @pcisar Test added. |
Modified by: @pavel-zotovstatus: 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] |
Submitted by: Tim Barber (tim.barber)
Is related to CORE1647
Is related to QA237
In 2.1.2 SuperServer, any data written to external tables are visible to other sessions.
However in Classic, this data is not visible. It seems to be cached and written to file eventually, when this happens it becomes visible.
Super Server behaviour:
We created a new external table.
In session A we inserted data with no commit. The external table file was showing 0 size.
Started session B and selected data from the external table. The data was returned, and this triggered the a file flush and the external table file now shows the data (viewing the file in Windows).
Committed session A and data visibility still behaves correctly.
Classic behaviour:
We created a new external table.
In session A we inserted data with no commit. The external table file was showing 0 size.
Started session B and selected data from the external table. No data was retuned and the external table file is still 0 size.
Select from external table using session A or Commit or disconnect session A and the data is flushed to the file. It is now visible from session B.
Commits: 915429e 7c9a94b
====== Test Details ======
THIS TEST WILL END WITH ERROR IF EXTERNAL TABLE ACCESS IS NOT ALLOWED, WHICH IS BY DEFAULT.
It's necessary to adjust firebird.conf
The text was updated successfully, but these errors were encountered: