Convertin v1.1 to v3.5.2 - ???

[Ivan Smahin]

Hello Barry,

Friday, April 4, 2008, 1:29:34 AM, you wrote:

> "Important is that ObjectPtr field point the same LOGICAL record as it was
> in v1."

> Yes, that is the important point, regrettably, it doesn't convert properly.

> Even if the ObjectPtr has a new converted value that new converted value
> should point to the same previous/pre-conversion/correct LOGICAL record.

But why do you think that "pointed table" RecIDs stays unchanged?

Look, there is some table t1.
Create table t1 ( f1 long );

--insert 3 records.
INSERT INTO t1 VALUES( 1 )
INSERT INTO t1 VALUES( 2 )
INSERT INTO t1 VALUES( 3 )

--drop second record
delete from t1 where RecID = 2

--now you see:
select RecID from t1

1
3

Second record has RecID equal to 3.
Assume there is some t2 table which contains the ObjectPtr field
pointed to t1. It must be "3" to point to the second record - right?

Now you do Clone or Convert or Dump load. All such operations
"eliminate" RecID-holes - so t1 now looks like:

RecID     f1
------------
1         1
2         3


Certainly - any ObjectPtr field pointed to the second record now contains
"2" instead of "3".


> Is the value of the ObjectPtr supposed to be the foreign tables RecID?
Exactly.

-- 
Best regards,
Ivan Smahin 
Senior Software Engineer
Paradigma Software, Inc
Valentina - The Ultra-Fast Database
http://www.valentina-db.com