RE: [Reactor for CF] DAO generation and Oracle 10

[Van Daele Wouter \(DBB\)]

Thanks all - it just shows that I'm a relative newbie to Oracle ;-)

 

I hope Oracle agrees with me that primary keys should be unique as well <grin>

 

Wouter

---

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Teddy Payne
Sent: dinsdag 25 juli 2006 19:53
To: reactor@doughughes.net
Subject: Re: [Reactor for CF] DAO generation and Oracle 10

Also, indexing is applied differently to unique versus primary keys.

On 7/25/06, Brian Kotek <[EMAIL PROTECTED] > wrote:

A primary key, is, well, the primary key for the table. A unique constraint just means the values in that column have to be unique. I suppose the main difference is that a table can have only one primary key, but can have numerous unique column constraints. Hope that helps.

Brian

On 7/25/06, Van Daele Wouter (DBB) < [EMAIL PROTECTED]> wrote:

I've tried that, and lo and behold: it works!

 

Could someone briefly explain the difference between PRIMARY and UNIQUE ?

 

W.

---

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] ] On Behalf Of Van Daele Wouter (DBB)
Sent: dinsdag 25 juli 2006 17:25
To: reactor@doughughes.net
Subject: RE: [Reactor for CF] DAO generation and Oracle 10

Beth,

 

Nope - all lines for the "primaryKey" attribute say "false".

 

And yet I have a constraint of type "UNIQUE" on the CATEGORYID column... I suppose that type should be PRIMARY, and not UNIQUE ?

 

Wouter

---

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] ] On Behalf Of Beth Bowden
Sent: dinsdag 25 juli 2006 15:24
To: reactor@doughughes.net
Subject: Re: [Reactor for CF] DAO generation and Oracle 10

Van,

In your categoryMetadata.cfc, is there a line similiar to:

               <cfset variables.metadata.fields[1]["primaryKey"] = "true" />

?

Thanks, Beth

On 7/25/06, Van Daele Wouter (DBB) <[EMAIL PROTECTED] > wrote:

(Can't seem to get logged in to the Reactor Trac site, so I'm logging it here...)

Doug, all,

This morning I downloaded revision 330 of Reactor, cleared the project directory and restarted my app. Unfortunately, I'm still getting badly formed DAO's for all my tables with a (single) primary key. Create and Read are OK; Save, Update and Delete are flawed...

From what I had to do to get my app running, I'ld say that the primary keys aren't detected by Reactor (cf. Trac ticket #41 http://trac.reactorframework.com/reactor/trac.cgi/ticket/41 ). Example: here's the Save function as currently generated:

        <cffunction name="save" access="public" hint="I create or update a CATEGORY record." output="false" returntype="void">

                <cfargument name="to" hint="I am the transfer object for CATEGORY" required="yes" type="reactor.project.qtau.To.CATEGORYTo" />

                <cfset create(arguments.to) />
        </cffunction>

There's no way this code can decide between "create" and "update"...

Similarly, the generated Update and Delete methods end with:

                        ...
                        WHERE
                </cfquery>
        </cffunction>

No comments needed, I suppose. This problem is blocking my progress with an app that has to be finished soon; in the current state of affairs I'll have to code my  DAO's and Gateways by hand - without Reactor...

<no fun>

W.

-------------------------------------- Dexia Bank disclaimer : http://www.dexia.be/maildisclaimer.htm --------------------------------------

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Reactor for ColdFusion Mailing List
reactor@doughughes.net
Archives at: http://www.mail-archive.com/reactor%40doughughes.net/
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Reactor for ColdFusion Mailing List
reactor@doughughes.net
Archives at: http://www.mail-archive.com/reactor%40doughughes.net/
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

------------------------------------------------------------- Dexia Bank disclaimer : http://www.dexia.be/maildisclaimer.htm -------------------------------------------------------------

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Reactor for ColdFusion Mailing List
reactor@doughughes.net
Archives at: http://www.mail-archive.com/reactor%40doughughes.net/
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

------------------------------------------------------------- Dexia Bank disclaimer : http://www.dexia.be/maildisclaimer.htm -------------------------------------------------------------

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Reactor for ColdFusion Mailing List
reactor@doughughes.net
Archives at: http://www.mail-archive.com/reactor%40doughughes.net/
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Reactor for ColdFusion Mailing List
reactor@doughughes.net
Archives at: http://www.mail-archive.com/reactor%40doughughes.net/
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

--
<cf_payne />
http://cfpayne.wordpress.com/
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Reactor for ColdFusion Mailing List
reactor@doughughes.net
Archives at: http://www.mail-archive.com/reactor%40doughughes.net/
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

------------------------------------------------------------- Dexia Bank disclaimer : http://www.dexia.be/maildisclaimer.htm -------------------------------------------------------------

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Reactor for ColdFusion Mailing List
reactor@doughughes.net
Archives at: http://www.mail-archive.com/reactor%40doughughes.net/
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --