|
The base dao.cfc has an “exists”
function that returns true or false if the record already exists. Beth Bowden Phone: 919-541-3355 FAX: 919-541-3687 From: Brian Kotek
[mailto:[EMAIL PROTECTED] Just thought I'd ask in case I'm missing something within the API. I
just realized that if a user attempts to insert a duplicate record using the
same primary key values as an existing record, when you call save() reactor
will treat it as an UPDATE instead of throwing an error due to a duplicate
primary key. I'm sure I could create something that checks to see if the record
already exists (which is really what save() does under the hood) and skip the
save(), but I wanted to ask the group first if they have any other ideas.
Thanks. |
RE: [Reactor For CF] Duplicate Insert vs. Update?
Bowden, Beth \(NIH/NIEHS\) [E] Wed, 26 Apr 2006 11:07:24 -0700
- [Reactor For CF] Duplicate Insert vs. Updat... Brian Kotek
- RE: [Reactor For CF] Duplicate Insert ... Bowden, Beth \(NIH/NIEHS\) [E]
- Re: [Reactor For CF] Duplicate Ins... Brian Kotek
- RE: [Reactor For CF] Duplicate... Doug Hughes
- Re: [Reactor For CF] Dupli... Brian Kotek
- Re: [Reactor For CF] ... Doug Sims
- Re: [Reactor For ... Brian Kotek
- RE: [Reactor ... Bowden, Beth \(NIH/NIEHS\) [E]
- Re: [Reactor ... Brian Kotek
- RE: [Reactor ... Doug Hughes
- Re: [Reactor ... Brian Kotek
- Re: [Reactor ... Doug Arthur

