Case preserve behaviour [CORE1645] #2069
Submitted by: Eugenk Konkov (kes)
Is duplicated by CORE5766
For more details see 'Upper case behaviour' thread in mailing list 'firstname.lastname@example.org'
>It will be a problem.
Why are those not the same?
Another question: SQL says that object names must not be case sensetive
SECOND. Third party tools must not do any suggestion about queries, names and so on
Why tools suppose quoting in this case?
See next algorithm to do with quotes
I think this is VERY SAFE
>These are 3 different tables, obviously, MYTABLE can be used unquoted
AS I ALLOW same names in database like 'aa' and 'aA'
The text was updated successfully, but these errors were encountered:
Commented by: @ArnoBrinkman
Case preservation would be very nice as an option for the whole database
CREATE TABLE MyTable (ID INT) => Should store internally MyTable
IMO, all these queries should then work and return the same data
I cannot think of why i ever want to create 2 ore more objects with the "same" name, but different case-mixing into the database.