Err... give it a primary key? That's your best, safest solution.

If for some reason you don't want to give your table a pkey, then (since I've been a little out of the loop lately) I'm not sure what to tell you. There may be a workaround that I'm not aware of... though I still suggest that adding a primary key is your best idea.

Any reason why you can't?

Laterz,
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 Jul 29, 2006, at 6:08 AM, Kevin Roche wrote:

I tried using the key on the read and that worked but doesnot have the same
facility on save.

Can Anyone suggest a good way to update a record on a table without a
primary key?

Kevin

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Kevin Roche
Sent: 29 July 2006 11:58
Subject: [Reactor for CF] Table with no primary key


Hi,

I am using Reactor for the first time and of course it isn't in the easy
world I would like.

My table has no primary key!

Reactor seems to have problem with load and save (of a Record object) which
return multiple records and insert rather than update.

Am I right in thinking that specifying the key in the attributes is required
in both cases?

Kevin Roche



-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -
- --
Reactor for ColdFusion Mailing List
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -
- --




-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Reactor for ColdFusion Mailing List
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --



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

Reply via email to