G
gus
Guest
Havard mentions the problem of "errors on subsequent saves after an update that moved the record to another partition". that problem can occur when using table partitioning and you update a row's partition key value such that it has to go to a different partition. as a rule, that is not a good thing to to be doing but we recognize that there may be special circumstances in which you may have to do it. moving a row to another partition requires deleting it from its original location along with all its index entries and then creating it anew in another location along with new index entries. this can have a deleterious effect on performance if you do it a lot. therefore, though table partitioning is intended to be transparent to 4GL applications, when adding new rows, you had should make sure to assign the partition key value(s) before the row gets created.
Continue reading...
Continue reading...