Page 1 of 1
Text case of "special" names
Posted: Wed 03 Apr 2013 19:26
by sov
Hi,
We have table "User" with columns "Password" and "Description".
Despite having Identifier Case set as "As in the database" these names are lowercased after formatting.
Code: Select all
-- I expect:
select U.[Password], U.[Description] from Main.[User] as U
-- But get:
select U.[password], U.[description] from Main.[user] as U
Could you please provide information how to prevent this behaviour?
Thanks in advance!
Stefan.
Re: Text case of "special" names
Posted: Thu 11 Apr 2013 09:45
by alexa
If we are right, you were referring to SQL Complete v4.0.
This means that there are duplicate object names in the current database and SQL Complete stores the case of the first matched object in the database.
Please try using the 'Do not change' option rather than 'As in the database'. In this case objects will be inserted in the same case as they appear in the suggestion list.
Re: Text case of "special" names
Posted: Thu 11 Apr 2013 12:04
by sov
Thank you for the reply, but the ability to get the names as in the database was one of the mean reasons to choose SQL Complete.
So, 'do not change' is not a serious option.
I'm using trial version 4.0.70
If I understand you correctly, a columnname is only cached once and not per table?
Why not change the order in caching user objects first and system object last?
Re: Text case of "special" names
Posted: Thu 11 Apr 2013 13:09
by alexa
If I understand you correctly, a columnname is only cached once and not per table?
That's right.
Why not change the order in caching user objects first and system object last?
Most probably there are multiple user objects with the same column name in the database. SQL Complete doesn't divide objects into user objects and system objects.
Nevertheless, you can add your suggestions on our UserVoice forum where other users can vote for them:
http://devart.uservoice.com/forums/87893-sql-complete
Re: Text case of "special" names
Posted: Wed 15 Jan 2014 08:21
by sov
This seems to be fixed in version 4.5 !