Hi @SteveOstrowski 
Thanks for replying. I have few doubts. Could you help me clarify the same?

• You said, "..., the schema evolution logic detects that both NEST_COL and nest_col would resolve to the same column, which triggers the conflict error.".
  1. Could you explain why this results in an error? Because column names should be case insensitive and the names 'Nest_col', 'NEST_COL', 'NeSt_CoL', 'nest_col' should all point to the same column.

• You said, "... SET clause says NEST_COL = source.NEST_COL but the source view actually has nest_col (lowercase), the engine sees these as potentially two separate columns that would collide"
  1. Shouldn't the source treat them as same? Isn't that what case-insensitive should be about?
  2. Also, I may be misunderstanding. But your two statements seem to be conflicting with each other.