CGCLT > desc table t1;
+-----------+-----------+-----------+-----------+-----------+-----------+
| TABLEDESC | TABLEDESC | TABLEDESC | TABLEDESC | TABLEDESC | TABLEDESC |
|      ATTR |      TYPE |    LENGTH |       DIM |   DEFAULT |  NULLABLE |
+-----------+-----------+-----------+-----------+-----------+-----------+
|         a |       int |         4 |         0 |      null |       yes |
|         b |    string |       300 |         0 |      null |       yes |
+-----------+-----------+-----------+-----------+-----------+-----------+
2 tuples
ok ( 0.001 s )
CGCLT > select * from t1;
+-----------+-------+
|        t1 |    t1 |
|         a |     b |
+-----------+-------+
|         1 | Hello |
+-----------+-------+
1 tuples
ok ( 0.001 s )

select * from t1 where a = 42 or a = 1 and  b = 'X' ;
select * from t1 where a = 1 and  b = 'X' or a = 42;
select * from t1 where a = 42 or ( a = 1 and  b = 'X' );

drop if exists table t1;
create table t1 (
    a int,
    b int,
    c int);

insert into t1 values ( 1, 1, 10 );
insert into t1 values ( 1, 2, 20 );
insert into t1 values ( 2, 1, 5 );
insert into t1 values ( 2, 2, 42 );
insert into t1 values ( 2, 3, 42 );
insert into t1 values ( 3, 1, 1 );
insert into t1 values ( 3, 2, 65 );
insert into t1 values ( 3, 2, 12 );

drop if exists view v1;
create view v1 as
select
    a as a,
    b as b,
    sum ( c) as csum
from t1 group by a, b;

select a, b, csum from v1 where a = 3 and b = 2;

-- csum cannot not be evaluated in the view condition
-- cursor must perform a dedicated evaluation
select a, b, csum from v1 where a = 3 and b = 2 and csum = 77;

drop if exists table t1;
create table t1 (a  int, b string(10));

start transaction;
insert into t1 values ( 1, 'XXX'); 
insert into t1 values ( 1, 'XXX'); 
insert into t1 values ( 1, 'XXX'); 
-- here a double delete may occur
delete from t1;
commit;
insert into t1 values ( 1, 'XXX'); 
select * from t1;

case when t2.a = 1 
then
   case when  t2.b = t1.b
   then
	'VALID'
   else
         'INVALID'
   end
else
   'VALID'
end as status

 
   jdbc:cego:::<port>:

create table t1 ( a int, b string(10));
insert into t1 values ( 1, 'alpha');
create btree b1 on t1(b,a); -- inverted, value for a would be not setup correctly

select
        sum(b) as sc,
        case when sum(b) > 700 
                then 'X'
		else 'Y' end as xy
from t1;

create table t1 ( a int, b string(30));
insert into t1 values ( 1, 'DONE');
insert into t1 values ( 2, 'DONE');
insert into t1 values ( 3, 'WAIT');
insert into t1 values ( 4, 'DONE');
insert into t1 values ( 5, 'WAIT');
update t1 set b = 'DONE' where b = 'WAIT' return :a = a; 

create table t1 ( a int, d datetime);
create btree b1 on t1(b);
select a from t1 where b = '12.07.2019'; -- should be casted from string to datetime

insert into a1 values ( 1, 'XXX');

create table t1 ( a int, b string(10), c string(30))
create alias a1 on t1 ( a as ax, b as bx);

drop if exists table t1;
list alias;
desc alias a1;
drop if exists alias a1;
create table t1 ( a int, b string(30));
create alias a1 on t1 ( a as ax, b as bx );

insert into a1 ( ax, bx ) values ( 1, 'XXX');
insert into a1 ( ax, bx ) values ( 2, 'YYY');
insert into a1 ( ax, bx ) values ( 3, 'ZZZ');

select ax from a1;

NUMRUN=100
DOTRANSACTION=-dotransaction
ARANGE=10000
AINTERVAL=500
ACOUNT=30000
PRIMARY=primary
POOLSIZE=191

• Fix added in CegoTransactionManager::commitUpdate, btree must be inserted with insertBTreeWithCommit
• Fix added in CegoTransactionManager::getCrashAffectedTables, schema entry must be searched with Find(CegoField(Chain(), SYS_RB_TABLE))

• In CegoRecoveryManager::recoverCurrentTransactionLog crash affected tables are analyzed at the beginning now. This must be done, since commit or rollback operations may occur in the recovery log
• In CegoTransactionManager, getObjectWithFix method calls have been eliminated. The sustained fix on the pages avoids writing the pages during checkpoint, which may result in inconsistent rollback segments
• In CegoObjectManager::createTableObject, the getNewFilePage method call was moved to the beginning. It may happen, that a checkpoint occur during the method call, which may result in inconsitent table entries ( newEntry is called, during getNewFilePage a checkpoint is forced which writes the incomplete page to disk and just after the checkpoint, the table information is encoded

select left(a,3) from t1 => length 3 is used for schema
select left(a,b) from t1 => definition of a is used for schema

start transaction;
insert into t1 values ( 1, 'XXX');
update t1 set b = 'FFF' where a = 1; -- here comes a duplicate error
commit;

#define NETMNG_MAXTUPLECOUNT 3000
#define NETMNG_MAXBYTECOUNT 10000000

create view v1 as
select a as a, b as b from t1
union all
select a as a, 0 as b from t2;

  select nextcount(mycount);