Why do We Need CTXXPATH When ConText Indexes Can Perform XPath Searches?
The existing ConText index type already has some XPath searching capabilities, but the ConText index type has some limitations: For the ConText index to be usable as a primary filter for existsNode(), You must create the index using PATH_SECTION_GROUP. You cannot create the index with USER_LEXER or MULTI_LEXER preference. You must create the index with DIRECT DATASTORE. You must create the index with NULL FILTER. This limits the linguistic searching capabilities that ConText index type provides. The ConText index is asynchronous and does not follow the same transactional semantics as existsNode(). The ConText index does not handle namespaces nor user-defined entities. With all these limitations in mind, CTXXPATH index type was designed specifically to serve the purpose of existsNode() primary filter processing. You can still create ConText indexes with whichever preferences you need on XMLType columns, and this will be used to speed up CONTAINS operators. At the same time, you can crea
