Search

RETS Change Proposal 20: Special Search Token .ALL
Author: Brita Brodin
Organization: WyldFyre Technologies
Telephone: (408)369-8900
Address:
Email: brita@wyldfyre.com
Status: Proposal
Date: 12/09/2002
Proposal Version: 1.0
1. Synopsis
Currently, if a lookup field is required, the RETS search request has to contain every value defined for the lookup in the metadata. The RETS Query Language should contain a special search token such as .ALL. with means “all values defined for the lookup”.
2. Rationale
If a lookup has a long list of acceptable values, the query string gets to be very long and some RETS servers are not capable of parsing such long search requests. Also, it is inefficient for a server to have to parse such a request since sending all values for a lookup is logically equivalent to not sending the field at all. However, if the field is defined as required in the metadata, the client must send it and therefore, it would be much more efficient to use a search token that signifies all values. For example, if Area is defined as required, it would be much more efficient to send a request such as QUERY=(Area=.ALL.) than QUERY=(Area=A|B|C|D|E|F...).
3. Proposal
Section 7.7 Query Language should be amended to show the following:

Lookup := <any legal ALPHANUM value for the field as defined in the metadata>|.ALL.

4. Development Impact
RETS parsers will need to be changed to recognize the .ALL. token.
5. Compatibility
RETS 1.5 Servers would be required to support the .ALL. token to be compatible.
6. Proof/Need of Concept Examples
None.