Project

General

Profile

Bug #59

create a more general specification for queries

Added by Chad Berkley over 19 years ago. Updated over 17 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
marine
Target version:
Start date:
08/09/2000
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
59

Description

work on a way to search through different fields from
different standards making the query more general

History

#1 Updated by Chad Berkley about 19 years ago

This fix is in progress:
I have added the capability to have <returnfield> tags in a pathquery document
which tell querySpecification what fields to return in the query. I am now in
the process of creating the SQL that correspond to the selected fields.

#2 Updated by Chad Berkley about 19 years ago

First of all, I changed pathquery.dtd to allow for {0..N} <returnfield>
tags. The content of each field should be either a path or a leaf
element of an xml path that you want to search by. For example
<returnfield>title</returnfield would return any TEXT node whos parent
node has "title" in nodename. You may also include direct paths such as
<returnfield>resource/originator/individualName/surName</returnfield>.

The next visible change I made was to alter DBQuery to allow for the
usage of this field. By default, DBQuery.findDocuments() returns docid,
docname, doctype, doctitle, createDate, updateDate from the
xml_documents table. findDocuments() now adds the extra fields from the
returnfield tag to the Hashtable that it returns with the results.

#3 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 59

Also available in: Atom PDF