list4xt : Mailing list for the XT users community.

[list4xt] Re: Regexpr or not no Regexpr. ( Re: Supportforomquery(XPath query) )

New Message
• Reply
• Next message: Paul Tchistopolskii: "[list4xt] Fw: Managing semi-trivial sets of stylesheets."
• Previous message: Paul Tchistopolskii: "[list4xt] Re: Regexpr or not no Regexpr. ( Re: Support foromquery(XPath query) )"
• In reply to: Paul Tchistopolskii: "[list4xt] Re: Regexpr or not no Regexpr. ( Re: Support foromquery(XPath query) )"
• Next in thread: Simon St.Laurent: "[list4xt] Re: Support for omquery (XPath query)"
• Reply: Eric van der Vlist: "[list4xt] Re: Regexpr or not no Regexpr. ( Re: Supportforomquery(XPath query) )"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Paul Tchistopolskii wrote:
>
> From: Eric van der Vlist
>
> > > Is there some usecase which strongly forces regular expressions ?
> >
> > I must admit I haven't a real usecase... wouldn't it be convenient to
> > search (and replace) substrings (the XPath string functions are pretty
> > limited) ?
>
> It may be convinient, but should it live in the core instead of
> extension ? <xsl: value-of select = "re:replace($string, $old, $new)"/>

Of course, we have to differentiate what is core xslt and use other
namespaces for extensions.

To be interesting, it should be allowed in pattern matches as well :

<xsl:template match="/doc/chapter[re:match($regexp)]">

> > RDBMS are storing strongly structured data but still need a "like"
> > clause (and some of them (PostgreSQL) are providing regexp extensions
> > which are very convenient), I don't see why it wouldn't be the case with
> > XML documents !
>
> Some of 'LIKE' cases in SQL exist only because SQL is about 'strongly
> structured data', so people are serializing / deserializing objects into
> strings. With XML the same things will be serialized/deserialized into XML.
>
> I agree, there is one typical usage of LIKE for text searching. ( To find
> something related to some word in set of messages, for example).
>
> My exprience shows that instead of using LIKE-based design pattern, it
> is better to use some extra layer specialized on the 'real' search with indexes
> and other stuff ( and it is even better not to store messages in a database
> at all ;-)
>
> I think it could be better if LIKE not exist in SQL, because
> it usually forces 'bad' application logic. Even it provides a
> convenient and 'fast' solution. Like perl does ;-)

You will have a hard time if you want to force people to use 'good'
application logic :=)
 
> Rgds.Paul.
>

Eric

-- 
------------------------------------------------------------------------
Eric van der Vlist       Dyomedea                    http://cheapestmerchantaccounts.com
http://thepaymentguru.com -           http://adultstoresales.com              http://cristinasbookreviews.com
------------------------------------------------------------------------
--
Mailing list for the XT users community.     (http://thecallcentercorp.com)
(mailto:list4xt-request@4xt.org?Subject=unsubscribe to unsubscribe)

• Next message: Paul Tchistopolskii: "[list4xt] Fw: Managing semi-trivial sets of stylesheets."
• Previous message: Paul Tchistopolskii: "[list4xt] Re: Regexpr or not no Regexpr. ( Re: Support foromquery(XPath query) )"
• In reply to: Paul Tchistopolskii: "[list4xt] Re: Regexpr or not no Regexpr. ( Re: Support foromquery(XPath query) )"
• Next in thread: Simon St.Laurent: "[list4xt] Re: Support for omquery (XPath query)"
• Reply: Eric van der Vlist: "[list4xt] Re: Regexpr or not no Regexpr. ( Re: Supportforomquery(XPath query) )"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]