Am I missing something or do you sound
like a satisfied user?
Help! I can’t find the complaint!
Doug
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Teddy Payne
Sent: Wednesday, May 31, 2006
11:02 AM
To: [email protected]
Subject: Re: [Reactor For CF] Why
no exists() method for objects with auto_increment PK ?
I am just trying to
develop some good OR habits. A lot of times I assume data is there.
My data can't be wrong?!
My users are gremlins and I need to expose all to the light of day.
It may mean a little extra code, but the flow of loading data, check for a
dirty read, update the object, check for record existance and then updating the
record seems like a good habit that I may start using more often.
On 5/31/06, Doug
Hughes <[EMAIL PROTECTED]>
wrote:
Either way, exists should
always exist on the Dao. If the API isn't
consistent then it's not a good API. I don't plan to call it when
not
needed, but it does need to be there.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
On Behalf
Of Tom Chiverton
Sent: Wednesday, May 31, 2006 10:53 AM
To: [email protected]
Subject: Re: [Reactor For CF] Why no exists() method for objects with
auto_increment PK ?
On Wednesday 31 May 2006 14:57, Teddy Payne wrote:
> good read, having a safe save is just as important. So having
an exists()
> prior to trying to attemtpt an update is making more sense to me.
I'm not convinced Reactor should issue an exist() prior to calling update()
(or even save() !). Mind you, Reactor currently does call exist() when you
call save() on tables with non-auto inc. PK's, and uses that to switch from
save() to update() (if I read XSLT right !).
isDirty and exists() check two different things.
I think it should just be something you can use if you want to check.
> So Tom, I am on the band wagon man!
Want some new XSLT templates ? :-)
--
Tom Chiverton
****************************************************
This email is sent for and on behalf of Halliwells LLP.
Halliwells LLP is a limited liability partnership registered in England and
Wales
under registered number OC307980 whose registered office address is at
St James's Court Brown Street
Manchester M2 2JF. A
list of members is
available for inspection at the registered office. Any reference to a
partner in relation to Halliwells LLP means a member of Halliwells LLP.
Regulated by the Law Society.
CONFIDENTIALITY
This email is intended only for the use of the addressee named above and may
be confidential or legally privileged. If you are not the addressee
you
must not read it and must not use any information contained in nor copy it
nor inform any person other than Halliwells LLP or the addressee of its
existence or contents. If you have received this email in error
please
delete it and notify Halliwells LLP IT Department on 0870 365 8008.
For more information about Halliwells LLP visit www.halliwells.com.
We are pleased to announce that Halliwells LLP has been voted AIM Lawyer of
the Year at the 2005 Growth Company Awards
-- Reactor for ColdFusion Mailing List -- [email protected]
-- Archives at http://www.mail-archive.com/reactor%40doughughes.net/
-- Reactor for ColdFusion Mailing List -- [email protected]
-- Archives at http://www.mail-archive.com/reactor%40doughughes.net/
--
<cf_payne />
-- Reactor for ColdFusion Mailing List -- [email protected]
-- Archives at http://www.mail-archive.com/reactor%40doughughes.net/
