4 ms·
I remember running into problems with SQL stored procedures where column and table names were case-insensitive, so you don't know if you've properly typed all t
by chihuahua 6y ago
I remember running into problems with SQL stored procedures where column and table names were case-insensitive, so you don't know if you've properly typed all the column and table names. Until a customer in Turkey eventually installs it and you find out you've missed the proper capitalization of an identifier containing the letter "I", and the stored procedure fails.
- heavenlyblue 6y agoThis is what I usually think about whenever people say yay to Unicode in language identifiers.
- formerly_proven 6y ago"I" is in ASCII.
- a1369209993 6y ago"İ" and "ı" are not.
- Pxtl 6y agoHonestly, I'm very pro case-insensitivity, but my experience with SQL servers have impressively demonstrated how not to do it. For example, MS SqlPackage, used for deploying schema, is case-insensitive... But that also means changes to text constants within your stored procs do not get treated as changes.