Re: [basex-talk] ancestor axis i.c.w. fetched XML issue

, August 31, 2020 2:38 PM To: RobStapper Cc: basex-talk@mailman.uni-konstanz.de Subject: Re: [basex-talk] ancestor axis i.c.w. fetched XML issue Hey Rob, hallo Hans-Jürgen, I have completely revised the traversal of mixed database/fragment nodes for the ancestor and preceding/following axes. In some

Re: [basex-talk] ancestor axis i.c.w. fetched XML issue

gt;> Windows 10 >> >> >> >> *From: *Christian Grün >> *Sent: *Wednesday, August 26, 2020 6:21 PM >> *To: *RobStapper >> *Cc: *basex-talk@mailman.uni-konstanz.de >> *Subject: *Re: [basex-talk] ancestor axis i.c.w. fetched XML issue >> >>

Re: [basex-talk] ancestor axis i.c.w. fetched XML issue

{}#yiv1151269877 Bummer. I don’t see a work around either.   Rob.   Sent from Mail for Windows 10   From: Christian Grün Sent: Monday, August 31, 2020 9:22 AM To: RobStapper Cc: basex-talk@mailman.uni-konstanz.de Subject: Re: [basex-talk] ancestor axis i.c.w. fetched XML issue   Seems

Re: [basex-talk] ancestor axis i.c.w. fetched XML issue

Bummer. I don’t see a work around either. Rob. Sent from Mail for Windows 10 From: Christian Grün Sent: Monday, August 31, 2020 9:22 AM To: RobStapper Cc: basex-talk@mailman.uni-konstanz.de Subject: Re: [basex-talk] ancestor axis i.c.w. fetched XML issue Seems you’ve stumbled upon a classic [1

Re: [basex-talk] ancestor axis i.c.w. fetched XML issue

> > > > Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for > Windows 10 > > > > *From: *Christian Grün > *Sent: *Wednesday, August 26, 2020 6:21 PM > *To: *RobStapper > *Cc: *basex-talk@mailman.uni-konstanz.de > *Subject: *Re: [basex

Re: [basex-talk] ancestor axis i.c.w. fetched XML issue

: RobStapper Cc: basex-talk@mailman.uni-konstanz.de Subject: Re: [basex-talk] ancestor axis i.c.w. fetched XML issue Hi Rob, An interesting one. The mixing of external nodes and node fragments (which have different internal representations) caused some confusion. The issue has been fixed, a new

Re: [basex-talk] ancestor axis i.c.w. fetched XML issue

Hi Cristian, 😉 😊 😊 Issue solved. That’s why I have so much confidence in BaseX and it’s team. thnx, Rob Sent from Mail for Windows 10 From: Christian Grün Sent: Wednesday, August 26, 2020 6:21 PM To: RobStapper Cc: basex-talk@mailman.uni-konstanz.de Subject: Re: [basex-talk] ancestor axis

Re: [basex-talk] ancestor axis i.c.w. fetched XML issue

Hi Rob, An interesting one. The mixing of external nodes and node fragments (which have different internal representations) caused some confusion. The issue has been fixed, a new snapshot is ready to go [1]. All the best, hope you are fine, Christian [1] https://files.basex.org/releases/latest/

[basex-talk] ancestor axis i.c.w. fetched XML issue

Hi Christian, I encountered some inconsistency when using an fetched XML-node in combination with xpath’s ancestor-axis. I attached a small snippet. I expect an ancestor here. It works alright if the XML-node is not fetched from a document or in case of the parent-axis. Best Regards, Rob Sta