Changes for entering new records into xml_queryresult:
1. Added a function which checks if there is a record exsists in xml_returnfield table for a given combination of return fields. If a record is found, the id for the record is returned. otherwise a new record is created in the xml_returnfield table and the id of the new record is returned....
Added code for updating xml_queryresult for action=delete and action=update
For both actions, the entries in xml_queryresult are deleted.This works for action=update because deletion of entry is simple and the entries will be created again when the docid is part of a search result next time.
Added a function which gives back a string which is generated by sorting the returnfields requested for given query specifications
Modified the offset which is used for creating the resultset. This helps in fixing the 'more than 1000 enteries in IN query' bug on Oracle.
Added a check for eml2.0.1 documents in ContentTypeProvider.java
Using a variable to replace the hard code for namesapce in inserting record to xml_relation table.
Fixed a bug in the format of query result.
Formatting improvements.
Implement a new HarvesterServlet for running Harvester as a servlet. This eliminates the need to run Harvester in a terminal window. By default, the HarvesterServlet is commented out in lib/web.xml.tomcat(3,4,5). The user documentation will be modified to instruct Harvester administrators to uncomment the HarvesterServlet entry.
View revisions
Also available in: Atom