Hi @SteveOstrowski 

Thanks for replying. I got the process of how databricks processes the schema evolution command internally. It helps a lot.

As you mentioned there are 2 steps. First, is the explicit set statement which I wrote. This statement is processed case-insensitively, right? Because in SET clause i can write 'NEST_COL', 'NesT_Col' or any other casing and it would still point to the same column. I have some doubts then.

• Shouldn't the second step also follow case-insensitivity then? During second step when looking at source schema to determine if any source columns should be added to target, shouldn't the comparison be case-insensitive? The end user only writes the 'set' clause which is step 1 and is case-insensitive
• Also, considering the broader picture, since the query is supposed to be case-insensitive, shouldn't any sub-implementations take into consideration that the query is case-insensitive?