[#CORE-976] Synchronization of DSQL metadata cache objects in classic-server.

Firebird Core

Synchronization of DSQL metadata cache objects in classic-server.

Created: 24/Oct/06 10:23 AM Updated: 16/Jun/07 12:28 PM

Component/s:

Engine

Affects Version/s:

0.9, 0.9.4, 0.9.5, 1.0 RC1, 1.0 RC2, 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.5 Alpha 3, 1.5 Alpha 4, 1.5 Alpha 5, 1.5 Beta 1, 1.5 Beta 2, 1.5 Beta 3, 1.5 Beta 4, 1.5 RC1, 1.5 RC2, 1.5 RC3, 1.5 RC4, 1.5 RC5, 1.5 RC6, 1.5 RC7, 1.5 RC8, 1.5 RC9, 2.0 Beta 1, 2.0 RC1, 2.0 Beta 2, 2.0 RC2, 2.0 RC3, 2.0 RC4, 2.0 RC5, 2.0.0, 1.5.4, 2.0.1, 2.1 Initial

Fix Version/s:

2.1 Alpha 1

Time Tracking:

Not Specified

Description

« Hide

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

All

Comments

Work Log

Change History

Version Control

Subversion Commits

Sort Order:

[ Permalink | « Hide ]

Pavel Cisar added a comment - 16/Jun/07 10:16 AM

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.

[ Permalink | « Hide ]

Adriano dos Santos Fernandes added a comment - 16/Jun/07 12:28 PM

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.