Changes for zSQLgate, version 0.10

• Support for full-text searching, using MySQL syntax. (This WILL NOT WORK on most other back-end databases). It is configured by the new fulltext keyword, in access-point specifications of the form:

  access number = fulltext "field,field..."

• Fields in generated records now appear in the order that they are specified in the configuration file rather than alphabetically sorted.
• Repeated fields may now be included.
• When generating MARC records, a repeated subfield within an already created field now causes a new (repeated) field to be started.
• Presentation of SUTRS records may now by configured by means of a format sutrs section in the data section of a database's configuration, similar to the format xml section. If this is absent, then the server falls back to presenting the old-style default SUTRS record containing all fields in alphabetical order.
• Compound field-specifications no longer need begin with % in order to be recognised: merely containing % is sufficient.
• Compound fields now behave properly if they consist of multiple lines (i.e. contain embedded newlines). Previously, the embedded text-constants came out in the wrong order.
• Fields (both simple, and embedded within a compound field specification) may now be prefixed with a ?, meaning that they are not required to be non-null; if they are null, then they are omitted, (along with the immediately preceding constant string in the case of embedded fields).
• Tab characters (represented by \t) are now supported in strings, as well as newlines (\n).
• Strings in the configuration file may be concatenated using +, which allows long strings to be broken across lines.
• The configuration file is now automatically reloaded if it has changed, just before any search or retrieve request is handled.

Feedback to <mike@sql.z3950.org> is welcome!