Yes,
xdmp:node-replace and related update functions operate on nodes in databases
only. There should be in-memory manipulation functions in the Xquery commons
suite that can be found in the xqzone svn. You should be able to find more
details on this page: http://developer.marklogic.com/code/
K
Extremely helpful, thank you! I found Ryan Grimm's module to update
in-memory nodes. Perfect. Thanks again,
Shannon
On Aug 18, 2009, at 3:31 PM, Geert Josten wrote:
Yes,
xdmp:node-replace and related update functions operate on nodes in
databases only. There should be in-memory manipula
Hi
You get the error with just a single node-replace call?
Are you sure each argument is a single node?
If you left function-mapping on, it might not create the error you
think it would, so you could try adding the option
declare option xdmp:mapping "false";
to turn it off, then see if the err
to:general-boun...@developer.marklogic.com] On Behalf Of Christopher Hamlin
Sent: Monday, May 11, 2015 7:42 PM
To: MarkLogic Developer Discussion
Subject: Re: [MarkLogic Dev General] xdmp:node-replace
Hi
You get the error with just a single node-replace call?
Are you sure each argument is a
Hi,
You can't make two changes to the same node, but somehow that is what
is happening. In this case you are making two changes to
fn:doc("/olympus/pacer-xml/1155991_2:13-cv-00188")/case/parties/party[1]/representedBy/counsel/firmname
The definition says:
Cause
The applic
Hi Kary,
Send us the XML samples along with your code snippet (that you want to
perform exactly). I can help you to make it works.
Regards,
Indy
On Tue, May 12, 2015 at 9:11 PM, Christopher Hamlin
wrote:
> Hi,
>
> You can't make two changes to the same node, but somehow that is what
> is happe
...@developer.marklogic.com] On Behalf Of Christopher Hamlin
Sent: Tuesday, May 12, 2015 8:41 AM
To: MarkLogic Developer Discussion
Subject: Re: [MarkLogic Dev General] xdmp:node-replace
Hi,
You can't make two changes to the same node, but somehow that is what is
happening. In this case you are makin
ogic.com
[mailto:general-boun...@developer.marklogic.com] On Behalf Of Indrajeet Verma
Sent: Tuesday, May 12, 2015 9:17 AM
To: MarkLogic Developer Discussion
Subject: Re: [MarkLogic Dev General] xdmp:node-replace
Hi Kary,
Send us the XML samples along with your code snippet (that you want to perform
exactly
more cler to me
when reading it as a log file.
From: general-boun...@developer.marklogic.com
[mailto:general-boun...@developer.marklogic.com] On Behalf Of Kari Cowan
Sent: Tuesday, May 12, 2015 1:57 PM
To: MarkLogic Developer Discussion
Subject: Re: [MarkLogic Dev General] xdmp:node-replace
I'd check that such a node exists:
fn:doc(...)/calendar/approval_status
It looks like you are missing the namespace on the element steps.
On Mon, Feb 8, 2016 at 8:37 PM, Kari Cowan wrote:
> I have used this node-replace statement on other types of records and it
> works fine, but it doesn’t wo
neral-boun...@developer.marklogic.com
[mailto:general-boun...@developer.marklogic.com] On Behalf Of Christopher Hamlin
Sent: Monday, February 08, 2016 5:40 PM
To: MarkLogic Developer Discussion
Subject: Re: [MarkLogic Dev General] xdmp:node-replace
I'd check that such a node exists:
fn:do
om>>
Reply-To: MarkLogic Developer Discussion
mailto:general@developer.marklogic.com>>
Date: Tuesday, February 9, 2016 at 4:45 AM
To: MarkLogic Developer Discussion
mailto:general@developer.marklogic.com>>
Subject: Re: [MarkLogic Dev General] xdmp:node-replace
Thanks Chris – ok, s
gic.com>>
Date: Tuesday, February 9, 2016 at 4:45 AM
To: MarkLogic Developer Discussion
mailto:general@developer.marklogic.com>>
Subject: Re: [MarkLogic Dev General] xdmp:node-replace
Thanks Chris – ok, so the node existed, but I had to call reference them with
the namespace.. no
neral-boun...@developer.marklogic.com] On Behalf Of Kari Cowan
Sent: Tuesday, February 09, 2016 5:29 AM
To: MarkLogic Developer Discussion
Subject: Re: [MarkLogic Dev General] xdmp:node-replace
Thanks Geert. I did not do that. Will I still be able to follow that
recommendation or should I d
The xdmp:node-replace() call works against nodes in the database. By doing the
xdmp:eval() you're passing in a node which has been essentially decoupled from
its database context, thus the error message. If you pass a simple XPath as
the first argument, it'll work for you.
Now, that's assumin
15 matches
Mail list logo
