Beth, I think you are thinking of the readObject() function that which had a second query that was run in case a match was not found. I left that function unchanged for exactly the reason you said.
The query in the readFields()function contains no correction for case. What it does contain is what appears to be an unnecessary sub query which increases the time of the query by a factor of ten or more in my tests. If I am missing something, please let me know as I have not yet pushed this code to production :-) . Thanks. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Beth Bowden Sent: Monday, October 08, 2007 1:58 PM To: [email protected] Subject: Re: [Reactor for CF] Slow generation of files using Oracle and newest reactor Beau, Although Oracle tables are typically named in uppercase, they can be in lower or mixed case when created like so: create table "eScalatIOns" ...; If my memory serves me correctly, the SQL was changed to select a table using an exact match in case and, if an exact match was not found, then using an uppercase match. Since column names are plucked from the system tables, their case was always determined correctly. Yes, this decreases performance when generating reactor files but has advantages when creating code that works with multiple databases. FWIW, Beth CONFIDENTIALITY NOTICE: This e-mail may contain information that is privileged, confidential or otherwise protected from disclosure. If you are not the intended recipient of this e-mail, please notify the sender immediately by return e-mail, purge it and do not disseminate or copy it. -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Reactor for ColdFusion Mailing List [EMAIL PROTECTED] Archives at: http://www.mail-archive.com/reactor%40doughughes.net/ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
