Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: CONTEXT Options
Ed,
This from the documentation. Should point you in right
direction.
Regards,
Tim
NUMJOIN specifies the characters that, when they appear in a string of digits, cause ConText Option to index the string of digits as a single unit or word. For example, a period '.' may be defined as a NUMJOIN character because it often serves as a decimal point when it appears in a string of digits.
PRINTJOINS specifies the characters that join a word together when they appear
within the word. Words that contain PRINTJOINS characters are stored in the
text index exactly as they appear in the text. For example, if you define '-'
as a PRINTJOINS character, the word 'pseudo-intellectual' is stored in the text
index as 'pseudo-intellectual'.
SKIPJOINS specifies the characters that join a word together, but the
characters are not stored in the text index. For example, if you define '-' as
a SKIPJOINS character, the word 'pseudo-intellectual' is stored in the text
index as 'pseudointellectual'.
Note: The default values for NUMJOIN and NUMGROUP are determined by the NLS initialization parameters that are specified for the database. In general, you do not need to specify a value for either NUMJOIN or NUMGROUP when creating a Lexer preference using the BASIC LEXER Tile
begin
ctx_ddl.Set_attribute ('PRINTJOINS', '-*/');
ctx_ddl.create_preference ('DOC_LINK', 'Dash, star, slash', 'BASIC LEXER' );
end;
>'m running Oracle 7.3.3 with the context option. I have
>a LONG column that contains ascii text. Within the data
>is embedded phone numbers with and without embedded
>formatting (i.e. "123-456-7890" and/or "1234567890").
>
>Searches with CONTAINS '456' would locate the first form only.
>Searches with CONTAINS '1234567890' would locate the second form only.
>Searches with CONTAINS '123-456-7890' would not locate any rows.
>
>I'm using all default values when I set up my POLICY. Are there
>any options that I can use to cause searches to be a little more
>flexible? In the example above, I'd like a search on '456' to
>return both of those rows as hits.
>
Received on Wed Mar 11 1998 - 00:00:00 CST