All it was doing at the time was:
<cfset getTransfer().save(getTransferObject()) />
[This was in my BaseDecorator, so it was one global save for all objects]
I was going to put conditional transaction usage in there (so we could
bypass transfer's transactions for our unit testing), but since we've
decided against that, I have since taken it out.
It would be good to know of a better way to do what I was trying to do, though.
On Fri, Oct 2, 2009 at 3:52 PM, Mark Mandel <[email protected]> wrote:
> Sounds like a bug in your custom save() function.
>
> What is it doing?
>
> Mark
>
> On Thu, Oct 1, 2009 at 12:31 PM, Scott Brady <[email protected]> wrote:
--
-----------------------------------------
Scott Brady
http://www.scottbrady.net/
--~--~---------~--~----~------------~-------~--~----~
Before posting questions to the group please read:
http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer
You received this message because you are subscribed to the Google Groups
"transfer-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/transfer-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
