Mhh, what if you solved that problem a slightly different way?
For example, what if you had a CompositeList that, well, is a composite of two lists and uses your algorithm? By having composites of composites of composites etc. you might be able to handle an arbitrary amount of lists without complicating the algorithm...
Just a raw, wild idea, frankly.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Where I am right now is resisting putting the handleFound and handleMissing methods in an interface so I can stub them out. I think I'll just bite the bullet and try it.
This is running a query against the same table on 8-10 databases - dev, qa, prod, etc. I think the output will be an HTML table showing which ones have the same keys and values
I made a class to represent one database. It has connection info, a description and a collection of rows. It doesn't feel very cohesive so far.
I thought about your compositing type idea before and just couldn't get my head around it. With the two-list thingie, I've always had one as "master" so I could definitively say when something was "missing" or "extra" or represented an insert or delete. With this thing I think all I can know is the values match across the line or they don't. And really I think that's all that is interesting. [ August 28, 2006: Message edited by: Stan James ]
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi