Re: [Reactor For CF] interesting outcome

[Jared Rypka-Hauer]

Sounds like a good thing for a Reactor 1.5 patch: <uppercaseObjectNames value="true" /> Or something. :) Really, eventually I think I'd like to see Reactor use a <setting name="" value="" /> syntax over the explicit tags now used for settings. Either that or add a settings block to the config. I see this thing going so far that people may want to start storing config parameters for use in the Reactor objects. Anyway, I just wanted to put this down so it was recorded in the archive for later. I strongly recommend against adding anything like this to it now... let's get 1.0 out the door and get on with life. How're those diapers coming, Doug? :) J ------------------------------------------------ Jared C. Rypka-Hauer Continuum Media Group LLC http://www.web-relevant.com Member, Team Macromedia - ColdFusion "That which does not kill me makes me stranger." - Yonah Schmeidler On May 20, 2006, at 11:02 AM, Bowden, Beth (NIH/NIEHS) [E] wrote: Doug, Yes, you are correct. If you create the table using quotes, you can then access the table using the identical cases if you use quotes. The default in Oracle (that is, if table names/column names aren't quoted) is to create the metadata in system tables in uppercase. So if you use Reactor with existing tables, the tables were probably created w/o quotes and that metadata is stored in uppercase.  My guess is that most Oracle users don't commonly use quotes. That said, the work-around is easy enough - just remember to uppercase names in reactor.xml Beth Bowden -----Original Message----- From: Doug Hughes [mailto:[EMAIL PROTECTED]]  Sent: Friday, May 19, 2006 11:35 PM To: reactor@doughughes.net Subject: RE: [Reactor For CF] interesting outcome That's not correct - at least not with the version of Oracle that I tested the reactor code with.  I have versions of the blog and contact manager that work with oracle and use mixed case identifiers.  I think you have to quote them, but they are allowed.  That's why Reactor always quotes everything. Doug -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Bowden, Beth (NIH/NIEHS) [E] Sent: Friday, May 19, 2006 8:41 PM To: reactor@doughughes.net Subject: RE: [Reactor For CF] interesting outcome Doug, Table and column names are stored in Oracle system tables in uppercase. If the names are lowercased (or mixed case), the selects won't find the entries in the system tables. A simple uppercase will fix the problem. Beth ________________________________ From: Doug Hughes [mailto:[EMAIL PROTECTED]] Sent: Fri 5/19/2006 8:38 PM To: reactor@doughughes.net Subject: RE: [Reactor For CF] interesting outcome From my (limited) experience with oracle it doesn't require uppercase fields.  They can be in either case. Doug -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of wikiwikiman Sent: Friday, May 19, 2006 11:55 AM To: reactor@doughughes.net Subject: Re: [Reactor For CF] interesting outcome Since you're using Oracle, you had better make sure that all table and field names are uppercased (that's what Oracle reuires). If I'm not mistaken, the latest version of Reactor may well have a bug in this matter - try uppercasing your names in the reactor.xml file and try again... Wouter On 5/19/06, Douglas Knudsen <[EMAIL PROTECTED]> wrote: I have a table called mytable say with two columns fkone and fktwo. This table is a so called link table and both columns comprise the  primary key.  I'm using Oracle BTW.  Looking at the DAO for this table generated by reactor I see SQL like this UPDATE mytable SET WHERE fkone = ... AND fktwo = .... obviously this bombs out when I try to perform a save() on the mytable object. Am I breaking a best practise here?  Or is this a bug of some  sort? -- Douglas Knudsen http://www.cubicleman.com this is my signature, like it? -- Reactor for ColdFusion Mailing List -- reactor@doughughes.net -- Archives at http://www.mail-archive.com/reactor%40doughughes.net/