----- Original Message -----
From: "Zabach, Elke" <[EMAIL PROTECTED]>
To: "'Umberto'" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Friday, July 04, 2003 10:25 AM
Subject: RE: SAPDB 7.4 LIKE pattern matching ranges
<snip>
>
> > I'm not sure I understand the reasoning behind this. Since it already
> > supported '%' and '_' *in addition to* ranges, what benefit was there to
> > remove the ranges?
>
>
> In SQL-standard a '(' is a '(', nothing more, nothing less, no special
meaning.
> If one is looking for a '(', he can just write '(', no escape character
needed.
>
> If the ranges still existed, '(' has a special meaning, i.e. the beginning
of a range,
> and to be able to search for '(' you have to use escape-character. --> it
is not ANSI-like.
>
> Therefore, to be standard-conform we had to remove the ranges, sorry.
Ok, that's a reasonable explanation. Why not then choose something less
commonly found in data such as '[]%' (square brackets) instead of '()*' as
used in MS-SQL, Sybase, and Oracle?
This feature is extremely useful in the telecom industry when processing
millions of records per day requiring complex pattern matching and benefits
from the performance of using an index. Running under MS-SQL server has been
exceptional but we're moving everything from M$ over to Linux. SapDB seems
to be the best alternative to MS-SQL and Oracle for features and
performance. However, this is one sticky point that could dminish
performance by as much as 100x. :(
Couldn't this be made into a feature that's activated by the user at the
query level with a keyword as is currently done to select SQL emulation mode
(i.e. INTERNAL, ORACLE, ANSI)?
>
> Elke
> SAP Labs Berlin
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general