[Dataxi-sysdev] Major soseqkeys change

[Jyry K. <jy...@ne...>]

Hello

I got sick and tired with soseqkeys as the mechanism did not skip existing
values in the target table.

Yes, I know there should be no existing rows in the target table beyond
the last key in soseqkeys, and yes, in such a case it is system design
flaw, but still. I has happened too many times recently.

So, I reorganised soseqkeys and after adding a new column "serie" to
support different serias for the same table, I added another one that
defines the key column name.

Actually, this is a lot better model for two reasons.

1) Table can have more than one sequential keys
2) The "does it already exist in the target table" check can be performed.

The down side of the new model is, that transiton from the old
table+lastkey table structure to the new table+colname+serie+lastkey is
not easy and practially needs some manual labour to do that.
However, it is definetly worth it.

So be carefull before upgrading and applying new soseqkeys as the old
table should be dropped off.

The old setTable() method stilll exists as a wrapper for the new
setTarget(), but the sooner any code using setTable() is adjusted to use
setTarget() the less problems should occur.


Cheers,
--Jyry
C:-(    C:-/    C========8-O    C8-/    C:-(