I feel like Winnie-the-Pooh here, Ray. I'm not following you. Are you saying reserve a block of N IDs before starting the transaction, by incrementing by N the traditional next-seq-id control record thereby freeing the ctrl item for use by other processes? What's the point of the 2 sequential io text files? They are private to the particular process reserving said block of N IDs, right? Why not just manage in memory?
"Christopher Robin tried to teach it to me once, but it didn't." "What didn't?" said Rabbit. "Didn't what?" said Piglet. Pooh shook his head. "I don't know," he said. "It just didn't. - A A Miln, "The House at Pooh Corner" cds -----Original Message----- From: Ray Wurlod One approach is to determine in advance how many keys you'll need then generate and store these in a text file. As you work through the main loop, read them from the text file and write the successfully-used ones into another text file. (Sequential file I/O is not counted as part of the transaction.) When it comes time to commit, you can grab the successfully used ones and do whatever you need to do with them. ------- ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
