Project

General

Profile

Bug #14

metacat TEXT nodes limited to 4K characters

Added by Matt Jones over 19 years ago. Updated over 17 years ago.

Status:
Resolved
Priority:
Immediate
Assignee:
Category:
metacat
Target version:
Start date:
06/08/2000
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
14

Description

The current 4K character limit on metacat TEXT nodes is going to be limiting in
some cases. Need mechanism to split text nodes into multiple sibling TEXT
nodes, each no more than 4K. Can't use a LONG or LOB because they can't be put
in the WHERE clause of a SELECT. Using mutiple sibling TEXT nodes will cause
problems searching across the boundaries, but it is the best approach AFAIK.

History

#1 Updated by Matt Jones over 19 years ago

Fixed bug where TEXT nodes couldn't be longer than 4000 characters, which is the
maximum length of a VARCHAR2 field in Oracle. Now, if text exceeds the field
length, I break the text up into a series of TEXT nodes each of the max field
length, and the remainder in the last TEXT node. The only problem with this is
that our current search algorithms only will find phrases within a single TEXT
nodes, so if the search term spans the node boundary, the search algorithm will
not return a hit. I expect this is extremely rare, basically inconsequential.
But I will still log it as a bug.

#2 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 14

Also available in: Atom PDF