My latest use case for lists in LotusScript has been a home-grown "replication" mechanism between Notes and Oracle.
Each document holds the key and a hash (created by Oracle). In a first step, I populate a list of a custom data type (for key and hash) from all Notes documents.
While navigating through the Oracle result set, I delete each element from the list, where key and hash do match.
If the hash does not match, I update the document.
If the key is not in the list, I create a new document.
Finally, every element still found in the list after looping through the result set, must refer to a document, that no longer has a corresponding record in Oracle, so it gets marked for deletion.
Works like a charm and it's fast! Comparing 70000+ documents and records takes between 30 and 60 seconds, mainly depending on network traffic. I love lists.
My latest use case for lists in LotusScript has been a home-grown "replication" mechanism between Notes and Oracle.
Each document holds the key and a hash (created by Oracle). In a first step, I populate a list of a custom data type (for key and hash) from all Notes documents.
While navigating through the Oracle result set, I delete each element from the list, where key and hash do match.
If the hash does not match, I update the document.
If the key is not in the list, I create a new document.
Finally, every element still found in the list after looping through the result set, must refer to a document, that no longer has a corresponding record in Oracle, so it gets marked for deletion.
Works like a charm and it's fast! Comparing 70000+ documents and records takes between 30 and 60 seconds, mainly depending on network traffic. I love lists.