Wildcard Expansion Doesn't have right a case Follow
Whenever I use wildcard expansion for SQL queries, it puts all the cols in lower case. This makes the feature useless cause there are case-sensitive DBs and with the type of work I do I always have to assume my code will be run on a case-sensitive DB.
Here's what I mean...
Here's my table:
And here's the expansion:
Notice the cases are different?
The same problem exists with auto-complete.
Here I'm getting table suggestions. I've cases the table right in my query, but look at the suggestions... that table is lower-case.
So using the suggestion is useless cause again, you have to assume your code will be run against a case-sensitive DB.
Please sign in to leave a comment.
Hello Sean McCown,
Thank you for reaching Rider Forum.
I tried reproducing the issue, that you are experiencing, however, I could not. In my case expanding was case-sensitive:
Hence, could you please do the following:
.DotSettings.userfile near your sln (if any)
.DotSettingsfile near your sln (if any)
You may attache them to our shared storage at https://uploads.jetbrains.com/ and provide me with the upload ID.
Thank you in advance!
Looking forward to hearing from you soon.