Oracle8i interMedia Text Reference
Release 2 (8.1.6)

Part Number A77063-01

Library

Product

Contents

Index

Go to previous page Go to beginning of chapter Go to next page

Result Tables, 3 of 4


CTX_DOC Result Tables

The CTX_DOC procedures return results stored in a table. Before calling a procedure, you must create the table. The tables can be named anything, but must include columns with specific names and data types.

This section describes the following result tables and their required columns:

Filter Table

A filter table stores one row for each filtered document returned by CTX_DOC.FILTER. Filtered documents can be plain text or HTML.

When you call CTX_DOC.FILTER for a document, the document is processed through the filter defined for the text column and the results are stored in the filter table you specify.

Filter tables can be named anything, but must include the following columns, with names and datatypes as specified:

Table B-7
Column Name  Type  Description 

QUERY_ID 

NUMBER 

The identifier for the results generated by a particular call to CTX_DOC.FILTER (only populated when table is used to store results from multiple FILTER calls) 

DOCUMENT 

CLOB 

Text of the document, stored in plain text or HTML.  

Gist Table

A Gist table stores one row for each Gist/theme summary generated by CTX_DOC.GIST.

Gist tables can be named anything, but must include the following columns, with names and data types as specified:

Table B-8
Column Name  Type  Description 

QUERY_ID 

NUMBER 

Query ID. 

POV 

VARCHAR2(80) 

Document theme. Case depends of how themes were used in document or represented in the knowledge base.

POV has the value of GENERIC for the document GIST. 

GIST 

CLOB 

Text of Gist or theme summary, stored as plain text 

Highlight Table

A highlight table stores offset and length information for highlighted terms in document generated by CTX_DOC.HIGHLIGHT. Highlighted terms can be the words or phrases that satisfy a word or an ABOUT query.

If a document is formatted, the text is filtered into either plain text or HTML and the offset information is generated for the filtered text. The offset information can be used to highlight query terms for the same document filtered with CTX_DOC.FILTER.

Highlight tables can be named anything, but must include the following columns, with names and datatypes as specified:

Table B-9
Column Name  Type  Description 

QUERY_ID 

NUMBER 

The identifier for the results generated by a particular call to CTX_DOC.HIGHLIGHT (only populated when table is used to store results from multiple HIGHLIGHT calls) 

OFFSET 

NUMBER 

The position of the highlight in the document, relative to the start of document which has a position of 1.  

LENGTH 

NUMBER 

The length of the highlight. 

Markup Table

A markup table stores documents in plain text or HTML format with the query terms in the documents highlighted by markup tags. This information is generated when you call CTX_DOC.MARKUP.

Markup tables can be named anything, but must include the following columns, with names and datatypes as specified:

Table B-10
Column Name  Type  Description 

QUERY_ID 

NUMBER 

The identifier for the results generated by a particular call to CTX_DOC.MARKUP (only populated when table is used to store results from multiple MARKUP calls) 

DOCUMENT 

CLOB 

Marked-up text of the document, stored in plain text or HTML format 

Theme Table

A theme table stores one row for each theme generated by CTX_DOC.THEMES. The value stored in the THEME column is either a single theme phrase or a string of parent themes, separated by colons.

Theme tables can be named anything, but must include the following columns, with names and data types as specified:

Table B-11
Column Name  Type  Description 

QUERY_ID 

NUMBER 

Query ID 

THEME 

VARCHAR2(2000) 

Theme phrase or string of parent themes separated by colons (:). 

WEIGHT 

NUMBER 

Weight of theme phrase relative to other theme phrases for the document. 


Go to previous page Go to beginning of chapter Go to next page
Oracle
Copyright © 1996-2000, Oracle Corporation.

All Rights Reserved.

Library

Product

Contents

Index