Support case sensitive parsing

[mitar]

So by standard SQL queries are not case sensitive. But for me, this is problematic because I like to encode metadata information into database structures (like table names, column names, etc.) so that database introspection can work well. But then this means I have to quote all names all the time in all SQL queries.

So I would love if this package could support case sensitive parsing (and unparsing, #18). This could allow one to read (and rewrite) queries without changing the case.

I am mentioning this because as this package becomes more SQL standardized, it would be useful to keep some extensions available (like case sensitivity).

[benesch]

This package already preserves the case of identifiers. Do you have a specific example of something that doesn’t work for you?

[mitar]

Yes, but with other issues like #17 I would like just to make sure that this is a conscious decision to support and not something which disappears.

[benesch]

It absolutely is intentional! Normalization is intentionally left to the client. If we ever fold in normalization support, we’ll retain a dialect that performs no normalization (the generic dialect).

…

On Thu, Nov 21, 2019 at 7:07 PM Mitar ***@***.***> wrote: Yes, but with other issues like #17 <https://github.com/andygrove/sqlparser-rs/issues/17> I would like just to make sure that this is a conscious decision to support and not something which disappears. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <https://github.com/andygrove/sqlparser-rs/issues/144?email_source=notifications&email_token=AAGXSIA6USLCYZTO6XSPJHDQU4PCZA5CNFSM4JQJWRF2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEE4CPKY#issuecomment-557328299>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGXSIDIPD6YKFQ2XVO5NT3QU4PCZANCNFSM4JQJWRFQ> .