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

Synchronization of DSQL metadata cache objects in classic-server. [CORE976] #1380

Closed
firebird-automations opened this issue Oct 24, 2006 · 9 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @asfernandes

Sometimes a created object could not be accessed.
Done in HEAD.

@firebird-automations
Copy link
Collaborator Author

Modified by: @asfernandes

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

resolution: Fixed [ 1 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @asfernandes

description: Sometimes a created object could not be accessed.
Done in HEAD.

environment: Sometimes a created object could not be accessed.
Done in HEAD.

=>

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Version: 2.1 Initial [ 10160 ]

Version: 1.5.3 [ 10028 ] =>

Version: 1.5.2 [ 10027 ] =>

Version: 1.5.1 [ 10026 ] =>

Version: 1.5.0 [ 10025 ] =>

Version: 1.0.3 [ 10006 ] =>

Version: 2.0.0 [ 10091 ] =>

Version: 1.5.4 [ 10100 ] =>

Version: 2.0.1 [ 10090 ] =>

Version: 2.1.0 [ 10041 ] =>

Version: 3.0.0 [ 10048 ] =>

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Version: 2.0.1 [ 10090 ]

Version: 1.5.4 [ 10100 ]

Version: 2.0.0 [ 10091 ]

Version: 1.0.3 [ 10006 ]

Fix Version: 2.1 Alpha 1 [ 10150 ]

Fix Version: 2.1.0 [ 10041 ] =>

@firebird-automations
Copy link
Collaborator Author

Commented by: @pcisar

This is wonderful problem description. CVS comment that would link code changes to this ticket is also missing, so I can only take your word that some problem exists and it's now gone.

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

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

@firebird-automations
Copy link
Collaborator Author

Commented by: @asfernandes

Consider c1 and c2 as two connections, with classic server:

c1: isql
c1: create database 'x\.fdb';
c2: isql x\.fdb
c1: create table t \(n integer\);
c2: select \* from t;
c2: commit;
c1: drop table t;
c2: commit;
c2: create table t \(n integer\);
c2: select \* from t;
Statement failed, SQLCODE = \-104
invalid request BLR at offset 28
\-table id 128 is not defined

You see, c2 can create a table but can't use it.
It probably created with id 129, but our cache had a reference to id 128.

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Workflow: jira [ 11281 ] => Firebird [ 15365 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

QA Status: No test

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment