You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In postgres, these are not issues because unquoted column names should be made lowercase in the AST (as the official parser does). This also means that column names tend to be lowercase, too. Using casing is possible, though, so we don't want to convert everything to lowercase for postgres.
The text was updated successfully, but these errors were encountered:
As a sidenote (without completely understanding the entire context and history), I noticed that AS and as for aliasing are treated differently in postgresql, while they shouldn't.
I'm not sure I understand, but in case it helps, it looks like table aliases aren't converted to an alias node (but are Unshaped). In this case the "AS" keyword is stored as written, which might be causing the casing issues?
Currently, to workaround tsql issues...
In postgres, these are not issues because unquoted column names should be made lowercase in the AST (as the official parser does). This also means that column names tend to be lowercase, too. Using casing is possible, though, so we don't want to convert everything to lowercase for postgres.
The text was updated successfully, but these errors were encountered: