Oracle seems to be a difficult case in the RDMS world ;-) I had a bit of a run-in with our Oracle DB admins. Using Reactor I couldn't get to the tables I wanted, even though all the definitions and configs were correct... The problem was (is) that we're using special accounts (one for each application) to access our tables, and these users are currently required to identify tables by including the "Schema" name in the database space. E.g. we have to write
SELECT * FROM "SCHEMA"."TABLE" Reactor of course generates (no aliases) SELECT * FROM "TABLE" Since our DB admins don't like to change their habits (yes, the problem can be solved by reconfiguring Oracle and defining socalled private synonyms), and since this phenomenon is likely to pop up at other Reactor installations, I'll try to see if we can fix that with an extra parameter in the config file, a bit extra info in the Oracle convention, and a few changes to the XSL... In the meantime, I'm off for a week of holidays with the kids! See ya! Wouter -- Reactor for ColdFusion Mailing List -- [email protected] -- Archives at http://www.mail-archive.com/reactor%40doughughes.net/
