Oh I see... yeah, nasty one then.
Oracle has other issues thought, the database forcing capital case means we'll never be able to run CITE on Oracle before we provide a full schema renaming support anyways (spatial forces the table name _and_ the geometry column name to be uppercase).
The other nasty aspect of this issue, Oracle wise, is that the customary way to represent the boolean type is with a char(1) forced to assume only Y/N values: http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:6263249199595
Not sure wheter we have any chance to spot that the column is meant to be a boolean with a setup like that :( (the mapping layer would not only need to change the names, but also map the types, before we can run cite on Oracle... bah!)