I'll let someone else summarize. At this point I have been convinced by Dan that his proposal is the best way forward. And by rick and dan that we should just go ahead and store column level metadata for the collate info in the store, as well as in the language level per column metadata.
The key points that convinced me are: o Even though we are proposing a "single" collation per database, internally we need to support 2 per database to do the right thing for system catalogs. Once there are 2 we needed support in store to at the very least store metadata per conglomerate. o It looks like dan's proposal makes the runtime creation of the collated and non-collated objects easier. I don't understand all the places this affects, but anything that makes this easier seems good to me. Bryan Pendleton wrote:
I'm afraid I struggled a bit to follow all the threads about the new collation support. Would it be possible for someone to briefly summarize: - what the major issues are, and - what the primary proposals are thanks, bryan
