There are certain actions in the application that are controlled by stored procedures. As such, I decided to create a custom save() method on the DAO in question to handle using the stored procedures.
When I tested the changes, I recieved an error about <cftransaction> and how all the transactions needed to have the same username and password. After a bit of searching, I discovered that in the DAO created by Reactor, there is an optional argument to determine whether or not you want all of the 'save' operations to be run in side of <cftransaction>. The default will run the save() operation inside <cftransaction>
Since the stored procedures I am using contain their own SQL transaction clauses, I decided to forego the Reactor <cftransaction> and used object.save(false). This worked like a charm.
For the record, this may be in the documentation, but at the time I was trying to troubleshoot this issue, I did not have access to it.
2 comments