Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000008RUVp
project_key: SOA

In the 5.2 ER3, it seems that column aliases are ignored, or at least that's the impression Squirrel gives. If I run the below query
in 5.1, I can see the column header "ALTERNATE_ID".

If I run the exact same query in 5.2 ER3, with the same VDB, I get NySystemLogin as the column header. This probably has the potential to break a lot of our application code.

select p.NtSystemLogin AS ALTERNATE_ID FROM Entity_Model.RefData.Persons p LIMIT 10;