Another possibility is changing the extractor in such a way that the
property always will have a value.

like: substring(concat([xpathexpression],'00000000'),1,8)

This ensures that the value will be filled with eight zero's when the value
in the XML file is empty.
Now the property web_start will either have the value 00000000 or the actual
value from the XML file. Now your DASL queries will become a lot smaller
(and hopefully faster) because the whole part for checking on the empty
value can be removed.

<d:gte>
     <d:prop>
         <h:web_end />
    </d:prop>
    <d:literal>20090401</d:literal>
</d:gte>



Cheers

Nico Tromp



On Wed, Apr 1, 2009 at 2:04 PM, Ard Schrijvers <[email protected]>wrote:

> On Wed, Apr 1, 2009 at 12:56 PM, Jasha Joachimsthal
> <[email protected]> wrote:
> > Hi Nick,
> >
> > 2009/4/1 Nick Stolwijk <[email protected]>
> >>                <d:or>
> >>                    <d:gte>
> >>                        <d:prop>
> >>                            <h:web_end />
> >>                        </d:prop>
> >>                        <d:literal>20090401</d:literal>
> >>                    </d:gte>
> >>                    <d:eq>
> >>                        <d:prop>
> >>                            <h:web_end />
> >>                        </d:prop>
> >>                        <d:literal />
> >>                    </d:eq>
> >>                </d:or>
> >> To retrieve documents which have an enddate after today or an empty
> >> enddate, I retrieve no documents.
> >>
> >> This started to happen after a reload of our database yesterday. After
> >> the reload we have removed the index and let it rebuild. Are there any
> >> other things we have overseen? How can this happen?
> >>
> >
> >
> > It's not possible to search for empty values.
>
> Exactly, and I doubt how it could have ever worked...?  If you want to
> search for empty values, we normally extract a different property, for
> example web_end_length containing the string length of the property.
> <d:literal >0</d:literal> would then result in the results with no
> web_end property
>
> Ard
>
> > If you use Hippo Repository 1.2.16 there is a bug in the d:or in some
> cases,
> > see [1]. This has been fixed in Hippo Repository 1.2.17.
> >
> > [1] http://issues.onehippo.org/browse/HREP-278
> > --
> > Jasha Joachimsthal
> >
> ********************************************
> Hippocms-dev: Hippo CMS development public mailinglist
>
> Searchable archives can be found at:
> MarkMail: http://hippocms-dev.markmail.org
> Nabble: http://www.nabble.com/Hippo-CMS-f26633.html
>
>
********************************************
Hippocms-dev: Hippo CMS development public mailinglist

Searchable archives can be found at:
MarkMail: http://hippocms-dev.markmail.org
Nabble: http://www.nabble.com/Hippo-CMS-f26633.html

Reply via email to