Oh yea - this update is one of the harder things I've ever written. I suspect that there is more work to do.
However, that clean() method is used externally by the framework (if I recall correctly). It's not dangerous to call clean(), it's just going to make isDirty return false. Oh - that's another point. If, for whatever reason, your TO contains elements (other than functions) which can't be converted to strings then isDirty will always return true. About the wiki - I haven't had time recently. Doug -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of wikiwikiman Sent: Tuesday, April 18, 2006 6:10 PM To: [email protected] Subject: Re: [Reactor For CF] New Commit committed API design is hard, so a few hickups are to be expected (and that's what a mailling list is for, after all). Sean has already pinpointed a few areas that need clarification... Allow me to add a warning. On 4/18/06, Doug Hughes <[EMAIL PROTECTED]> wrote: > Records have an isDirty method. This basically compares the current state > of the object to the initial state of the object (or the state after > initing, loading, or saving the record). You can manually call the clean > method to clean a dirty record. Don't do this though. ;) If a method is "dangerous", or even superfluous, make it private or delete it from the API. By the way: would a "reload" not have the same effect? And now for something completely different: I have been adding a few pages to the Reactor Wiki ( http://reactor.wikispaces.com/ ). Corrections and additions are both very necessary, unless there is really nobody interested in a bit of documentation about Reactor... Happy coding/testing/... Wouter -- 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/
