A single statement runs at one timestamp. Thus your code sees the database at time t0. MarkLogic doesn't actually execute the database updates as they appear in your code. Instead, it gathers them up and executes them atomically at the end, advancing the timestamp if everything works. Take a look at <http://docs.marklogic.com/guide/app-dev/transactions> and especially <http://docs.marklogic.com/guide/app-dev/transactions#id_85012>.
Justin On Oct 2, 2015, at 8:35 AM, Andreas Hubmer <[email protected]<mailto:[email protected]>> wrote: Hello, I've found an issue with xdmp:forest-clear. xdmp:document-insert("test.xml", <root/>); xdmp:forest-clear(xdmp:database-forests(xdmp:database())); doc("test.xml") (: should be empty :) When executing the above multi statement transaction, I would expect an empty result. But instead <root/> is returned. When I execute doc("test.xml") manually some moments later, the expected empty result is returned. As a workaround I could use xdmp:document-delete(cts:uris()) but my assumption is that xdmp:forest-clear is much faster. Is that true? Is xdmp:forest-clear somehow asynchronous? Or is it maybe a visibility problem with deleted data? I run the code as admin user (just for testing). Regards, Andreas -- Andreas Hubmer IT Consultant EBCONT enterprise technologies GmbH Millennium Tower Handelskai 94-96 A-1200 Vienna Web: http://www.ebcont.com<http://www.ebcont.com/> OUR TEAM IS YOUR SUCCESS UID-Nr. ATU68135644 HG St.Pölten - FN 399978 d _______________________________________________ General mailing list [email protected]<mailto:[email protected]> Manage your subscription at: http://developer.marklogic.com/mailman/listinfo/general
_______________________________________________ General mailing list [email protected] Manage your subscription at: http://developer.marklogic.com/mailman/listinfo/general
