You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: ShakespeareFan00 [Submitted to the original trac issue database at 5.35am, Friday, 3rd July 2009]
Currently it's nominaly possible to query XAPI directly if you know the
specfic tag you want.
Would it be possible to consider allowing the use of regexp so that a queries like
node[name={?}{?}{?)ton Place] (which would match to "name=Repton Place" "name=Manton Place"
but not to name="Acton Place" or name="Mansfield Place" or "name=Childs Way")
or
node[source={}Yahoo!{}] (which would match to "source=Yahoo!","source= NPE;Yahoo!","source=Yahoo!;NPE")
could be obtained via a XAPI.
I appreciate that matching regexps/wildcards might impose a sever load though.
The text was updated successfully, but these errors were encountered:
Author: pnorman [Added to the original trac issue at 2.16am, Monday, 2nd April 2012]
Closing as this relates to the old XAPI which is no longer maintained. The new jxapi can be found at https://github.com/iandees/xapi-servlet and issues should be reported there.
With jxapi it would be prohibitively expensive to do a regexp server-side.
Reporter: ShakespeareFan00
[Submitted to the original trac issue database at 5.35am, Friday, 3rd July 2009]
Currently it's nominaly possible to query XAPI directly if you know the
specfic tag you want.
Would it be possible to consider allowing the use of regexp so that a queries like
node[name={?}{?}{?)ton Place] (which would match to "name=Repton Place" "name=Manton Place"
but not to name="Acton Place" or name="Mansfield Place" or "name=Childs Way")
or
node[source={}Yahoo!{}] (which would match to "source=Yahoo!","source= NPE;Yahoo!","source=Yahoo!;NPE")
could be obtained via a XAPI.
I appreciate that matching regexps/wildcards might impose a sever load though.
The text was updated successfully, but these errors were encountered: