Hi Mark,

I did have a quick look at those docs but the examples confused me
because none of them have a <cftransaction></cftransaction> block in
them.

If I do as suggested and put this kind of thing in my init method:

<cfset arguments.transaction.advise(this, "^save") />

Do I still use the <cftransaction> tags:

             <cftransaction>

                <cfscript>
                        newPage =
variables.instance.transfer.new("Admin.CmsPageContent");
 
newPage.setPage_content_text(arguments.pageText);
                        newPage.setPage_title(arguments.pageTitle);
                        newPage.setPage_header(arguments.pageHeader);
                        newPage.setCms_page_key(arguments.pageKey);
                        newPage.setEditor_id(arguments.editorId);
                        variables.instance.transfer.save(newPage);
                </cfscript>

                <cfset theInsertedId = newPage.getPage_content_id>

                <!--- Now update cms_page to set the new value --->
                <cfquery name="qUpdateCmsPage"
datasource="ds_web_content">
                        update cms_page
                        set     key_num_draft = <cfqueryparam
cfsqltype="cf_sql_integer"
value="#theInsertedId#">
                        where key_num = <cfqueryparam
cfsqltype="cf_sql_integer"
value="#arguments.pageKey#">
                        </cfif>
                </cfquery>

                </cftransaction>

Or is the whole method implicitly wrapped in a transaction?

Andrew.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to