Auto-complete table and field names uppercase

	SqlExplorer wrote:
	My Oracle database fields were defined as uppercase, and Sql Assistant is not returning that; it's being reinterpreted as lower case. This should be considered a bug, not a missing feature.

According to SysOp

SysOp wrote:

It appears that in Oracle in DB2 all object and column identifiers by default are stirred in system catalog tables in upper case, not in the original case they were coded by users (unless users specifically used name delimiters to save the correct casing. To remedy for the issue SQL Assistant automatically converts full upper case names to lower case. Without that conversion the resulting SQL queries look monstrous- - basically everything appears in uppers case.

which could be regarded as a minor/major inconvenience or even a bug. SA counters the anomaly Oracle caused by uppercasing everything with lowercasing everything which should make the query more human readable (at least most of the times). You would get them uppercase even if you used lower/mixed case if it depended on Oracle alone. So having them lowercase is a feature. Not being able to turn that feature off... Well, yes, that can be considered bug as well. I'd call it an incomplete feature (speaking of the original intention, that is).

While I disagree with your statement there is a new option in version 7 to preserve database imposed case.

if you want to be consistent, you should also call Oracle database behavior a bug. It's converting your code to upper case regardless of how you entered it if you're not using delimiters. Agree?

	SysOp wrote:
	While I disagree with your statement there is a new option in version 7 to preserve database imposed case. if you want to be consistent, you should also call Oracle database behavior a bug. It's converting your code to upper case regardless of how you entered it if you're not using delimiters. Agree?

What? What does that have to do, with Sql Assistant not interpreting the Oracle fields in the same case, as they were defined?

I don't care what Oracle does with their catalog tables. All I know, is that other tools are reading the case correctly. It doesn't matter to me, whether they are doing it by reading something other than the catalog tables. Oracle can do anything they want; but if some of my tools are able to compensate accurately, and one tool is not, then yes I think it's a missing feature.

Anyway, I have version 7, and am trying to see if it is interpreting the case correctly. It looks like it will be necessary, to with the DB Options again.