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

[RobStapper]

Christian,

I’m drilling down on every path in a context element embedded XML-file element. 
With on every step a search in the tree-structure back to the context-root.
it seems to works fine.

Thanks 

Indeed cheers,
Rob

Sent from Mail for Windows 10

From: Christian Grün
Sent: Monday, 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 cases, processing should 
even have become faster. Your testing feedback is welcome [1].

Cheers,
Christian

[1] https://files.basex.org/releases/latest/



On Mon, Aug 31, 2020 at 9:22 AM Christian Grün  
wrote:
Seems you’ve stumbled upon a classic [1]; and the problem is related: Inside 
“database nodes” we only have a parent, but no reference to the ancestors of 
main-memory nodes. One more nudge to eventually get this fixed.

[1] https://github.com/BaseXdb/basex/issues/919


On Sat, Aug 29, 2020 at 11:19 AM RobStapper  wrote:
Hi Christian,
 
☹ We’re not there quite yet. See attached snippet.
 
I’m still loosing my CONTEXT-element when starting the ancestor-axis from a sub 
element of the XML-file-element.
 
Best regards,
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 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/
 
 
 
On Wed, Aug 26, 2020 at 2:37 PM RobStapper  wrote:
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 Stapper
 
Sent from Mail for Windows 10
 
 

Virus-free. www.avast.com
 
 



--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

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

[Christian Grün]

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 cases, processing
should even have become faster. Your testing feedback is welcome [1].

Cheers,
Christian

[1] https://files.basex.org/releases/latest/



On Mon, Aug 31, 2020 at 9:22 AM Christian Grün 
wrote:

> Seems you’ve stumbled upon a classic [1]; and the problem is related:
> Inside “database nodes” we only have a parent, but no reference to the
> ancestors of main-memory nodes. One more nudge to eventually get this
> fixed.
>
> [1] https://github.com/BaseXdb/basex/issues/919
>
>
> On Sat, Aug 29, 2020 at 11:19 AM RobStapper 
> wrote:
>
>> Hi Christian,
>>
>>
>>
>> ☹ We’re not there quite yet. See attached snippet.
>>
>>
>>
>> I’m still loosing my CONTEXT-element when starting the ancestor-axis from
>> a sub element of the XML-file-element.
>>
>>
>>
>> Best regards,
>>
>> Rob
>>
>>
>>
>> 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-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/
>>
>>
>>
>>
>>
>>
>>
>> On Wed, Aug 26, 2020 at 2:37 PM RobStapper 
>> wrote:
>>
>> 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 Stapper
>>
>>
>>
>> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for
>> Windows 10
>>
>>
>>
>>
>>
>>
>> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=emailclient_term=icon>
>>
>> Virus-free. www.avast.com
>> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=emailclient_term=link>
>>
>>
>>
>>
>>
>

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

[Hans-Juergen Rennau]

 PS: Rob - so do I.

Am Montag, 31. August 2020, 12:13:02 MESZ hat RobStapper 
 Folgendes geschrieben:  
 
 #yiv1151269877 #yiv1151269877 -- _filtered {} _filtered {} _filtered 
{}#yiv1151269877 #yiv1151269877 p.yiv1151269877MsoNormal, #yiv1151269877 
li.yiv1151269877MsoNormal, #yiv1151269877 div.yiv1151269877MsoNormal 
{margin:0in;font-size:11.0pt;font-family:sans-serif;}#yiv1151269877 a:link, 
#yiv1151269877 span.yiv1151269877MsoHyperlink 
{color:blue;text-decoration:underline;}#yiv1151269877 
.yiv1151269877MsoChpDefault {} _filtered {}#yiv1151269877 
div.yiv1151269877WordSection1 {}#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 you’ve stumbled upon a classic [1]; and the problem is related: Inside 
“database nodes” we only have a parent, but no reference to the ancestors of 
main-memory nodes. One more nudge to eventually get this fixed. 

  

[1] https://github.com/BaseXdb/basex/issues/919

  

  

On Sat, Aug 29, 2020 at 11:19 AM RobStapper  wrote:


Hi Christian,

 

☹ We’re not there quite yet. See attached snippet.

 

I’m still loosing my CONTEXT-element when starting the ancestor-axis from a sub 
element of the XML-file-element.

 

Best regards,

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 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/

 

 

 

On Wed, Aug 26, 2020 at 2:37 PM RobStapper  wrote:


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 Stapper

 

Sent from Mail for Windows 10

 

 

| 

 | 
Virus-free. www.avast.com 
 |



 


 

  
  

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

[RobStapper]

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]; and the problem is related: Inside 
“database nodes” we only have a parent, but no reference to the ancestors of 
main-memory nodes. One more nudge to eventually get this fixed.

[1] https://github.com/BaseXdb/basex/issues/919


On Sat, Aug 29, 2020 at 11:19 AM RobStapper  wrote:
Hi Christian,
 
☹ We’re not there quite yet. See attached snippet.
 
I’m still loosing my CONTEXT-element when starting the ancestor-axis from a sub 
element of the XML-file-element.
 
Best regards,
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 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/
 
 
 
On Wed, Aug 26, 2020 at 2:37 PM RobStapper  wrote:
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 Stapper
 
Sent from Mail for Windows 10
 
 

Virus-free. www.avast.com
 
 



--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

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

[Christian Grün]

Seems you’ve stumbled upon a classic [1]; and the problem is related:
Inside “database nodes” we only have a parent, but no reference to the
ancestors of main-memory nodes. One more nudge to eventually get this
fixed.

[1] https://github.com/BaseXdb/basex/issues/919


On Sat, Aug 29, 2020 at 11:19 AM RobStapper  wrote:

> Hi Christian,
>
>
>
> ☹ We’re not there quite yet. See attached snippet.
>
>
>
> I’m still loosing my CONTEXT-element when starting the ancestor-axis from
> a sub element of the XML-file-element.
>
>
>
> Best regards,
>
> Rob
>
>
>
> 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-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/
>
>
>
>
>
>
>
> On Wed, Aug 26, 2020 at 2:37 PM RobStapper  wrote:
>
> 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 Stapper
>
>
>
> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for
> Windows 10
>
>
>
>
>
>
> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=emailclient_term=icon>
>
> Virus-free. www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=emailclient_term=link>
>
>
>
>
>

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

[RobStapper]

Hi Christian,

☹ We’re not there quite yet. See attached snippet.

I’m still loosing my CONTEXT-element when starting the ancestor-axis from a sub 
element of the XML-file-element.

Best regards,
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 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/



On Wed, Aug 26, 2020 at 2:37 PM RobStapper  wrote:
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 Stapper
 
Sent from Mail for Windows 10
 


Virus-free. www.avast.com



--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
<>

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

[RobStapper]

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 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/



On Wed, Aug 26, 2020 at 2:37 PM RobStapper  wrote:
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 Stapper
 
Sent from Mail for Windows 10
 


Virus-free. www.avast.com



--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

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

[Christian Grün]

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/



On Wed, Aug 26, 2020 at 2:37 PM RobStapper  wrote:

> 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 Stapper
>
>
>
> Sent from Mail  for
> Windows 10
>
>
>
>
> 
>  Virus-free.
> www.avast.com
> 
> <#m_-4205430713949874543_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>