PL/SQL Developer ignores the double quotes in object names

[_Denis_]

PL/SQL Developer has problems to edit objects than name has double quotes.
For example:
There is a table with name ""Table1"". If I take to edit this table in PL/SQL Developer then after click "Apply" it is created new table with name TABLE1.
PL/SQL Developer ignores the double quotes.
Is any way to decided this problem?
Thanks.

 

[vladzak]

I second this - I posted a request here quite a while ago regarding objects in mixed case (Java classes in particular,) that require double quote enclosure, but the problem is still here. I think the easiest way to fix this is to enclose *all* object names in double quotes regardless their case, as most other tools do.

 

[CTzen]

>Is any way to decided this problem?

not to use identifiers in double quotes ?-)

>I think the easiest way to fix this is to enclose *all* object names in double quotes regardless their case, as most other tools do.

that would be, imho, the wrong way to "fix" it.

 

[_Denis_]

It is funnily that this problem is not fixed up to now.

 

[vladzak]

Originally posted by CTzen:
> I think the easiest way to fix this is to enclose *all* object names in double quotes regardless their case, as most other tools do.

that would be, imho, the wrong way to "fix" it.

Why? Oracle does it (take DBMS_METADATA for instance, or export/datapump) so why should not PL/SQL Developer? It's very easy to implement and covers all possible cases.

 

[CTzen]

1) IMHO, DBMS_METADATA & exp do that to take care of the "CooL taBLe nAmes" some tools and developers create.

2) It's error-prone. If you by mistake put a lower case character between quotes, there is a big risk, that other applications which don't use quotes or don't know exact name wont see it.

3) It looks ugly, imho.

 

[vladzak]

1) They do it because it's standard way to enclose *all* identifiers regardless their case.
2) Not more error-prone than not enclosing identifiers in double quotes, especially with databases migrated from other platforms where mixed-case identifiers are a norm. Applications that "don't know exact name"? What's that? How can an application working with a schema not know object names it works with? And even if it doesn't - when did catalog become obsolete?
3) So what?

Ok, I can partially agree with your argument - me personally don't need this functionality anywhere but Java stored procedures, but as I said in 2), there are quite a lot of databases where mixed-case identifiers are normal, and applications ported to Oracle from such databases usually preserve the names. PL/SQL currently doesn't allow to work with such ported applications. The fix is trivial, so why not implement it? They can even make it a preference, something along the lines of "Enclose ALL identifiers in double quotes" and enable it for Java objects regardless the setting.

 

[William Robertson]

Perhaps it wouldn't be too hard to check whether the name stored in the database was uppercase, and if not then double-quote it. Obviously double-quoting all names would be disastrous for readability.