This content has been marked as final. Show 4 replies
THATS WHY I ALWAYS PUT ALL ALEX IDENTIFIERS IN UPPERCASE ;)
Then how would the unfortunate few who work with "Mixed_Case_Tables" get their information?
Since by default Oracle database identifiers are case insensitive what is obviously required is for the APEX team to fix this bug (by making the process work with the identifiers as entered, not by adding <tt>upper</tt>), and for the deluded few requiring case sensitivity to use quoted identifiers.
A similar unfortunate situation exists in declarative BLOB support, where contrary to all Oracle norms, case sensitive identifiers are documented as being required. Since double quotes don't/can't play any role in the APEX process there, it's difficult to see why this unconventional convention is imposed, rather than requiring a very small minority to use the double quotes they must be using everywhere else.
"deluded few" :-)