Hi John, Thnx. Looking at the example again I now notice that there is a semi-colon after the xdmp:commit. I overlooked that earlier. :-/
Bit pity though. The transaction enables to span a commit over multiple requests (doing multiple requests before deciding to commit or rollback), but I was hoping it would also allow doing multiple transactions within a single request, *without* needing that semi-colon.. :-/ Kind regards, Geert -----Oorspronkelijk bericht----- Van: [email protected] [mailto:[email protected]] Namens John Snelson Verzonden: vrijdag 16 december 2011 11:42 Aan: [email protected] Onderwerp: Re: [MarkLogic Dev General] CORB processing continuation query. On 15/12/11 11:15, Geert Josten wrote: > About 1) I'm a bit confused. The example in the docs tell that you can > fetch a doc directly after a xdmp:commit from an insert just before the > commit. Something that is not possible without the commit. How is that > possible when the commit is postponed till the end of the execution? Kind > of temp working space only visible to that statement? And is it then true > that after the commit, the doc is not searchable yet? As the indexing > exceptions haven't occurred yet, so I assume it is not indexed either? You can use a semi-colon (";") to separate multiple XQuery statements (main modules) in the same file. A subsequent statement will be able to see the updates performed in the previous statement - but a commit is not necessary for this. When the statement ends, the updates are performed and _you_ can see the results of those updates. When a commit is performed, every other request in MarkLogic can see the results of your transaction's updates. John -- John Snelson, Senior Engineer http://twitter.com/jpcs MarkLogic Corporation http://www.marklogic.com _______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general _______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
