Skip to content
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

Closed
firebird-issue-importer opened this issue May 27, 2009 · 12 comments

Comments

@firebird-issue-importer

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

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented May 27, 2009

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.

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented May 28, 2009

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:
http://www.volny.cz/iprenosil/interbase/ip_ib_isc4.htm
Implementation like this would not work with out inter-session visibility.

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented May 30, 2009

Modified by: @hvlad

assignee: Vlad Khorsun [ hvlad ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented May 30, 2009

Commented by: @hvlad

Before v2.1 external table's IO was performed without caching and thus was very slow.
In v2.1 caching was turned on but it introduced side effect reported here. There is no issue in SS as written data flushed on first read after write.
But in CS we have an issue.

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jun 3, 2009

Modified by: @hvlad

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 2.5 RC1 [ 10300 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jun 5, 2009

Commented by: @hvlad

Backported into 2.1.3

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jun 5, 2009

Modified by: @hvlad

Fix Version: 2.1.3 [ 10302 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Nov 9, 2009

Modified by: @pcisar

Link: This issue is related to CORE1647 [ CORE1647 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Nov 16, 2009

Modified by: @pcisar

Link: This issue is related to QA237 [ QA237 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Apr 26, 2013

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Apr 26, 2013

Commented by: @pcisar

Test added.

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented May 29, 2015

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.
It's necessary to adjust firebird.conf

Test Specifics: [Custom configuration required]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants