Reported by Santa Barbara:
Interesting issue when working with non-integer indices. One of our databases has a “CatalogNumber” field that is populated with mostly integers, but it is in fact a string type (leading zeros and infrequent alphanumerics). On Specify6, we were able to use operators like “<“ with this field. In specify7, that query flags with a red field, and returns a set of records that aren’t readable in the records window. It looks like it gets passed to the database, which returns the same number of records each time.
More serious, it won’t work with “=“ either. Screen shot:
The way the same field looks in 6 in the query:
Reported by Santa Barbara:
Interesting issue when working with non-integer indices. One of our databases has a “CatalogNumber” field that is populated with mostly integers, but it is in fact a string type (leading zeros and infrequent alphanumerics). On Specify6, we were able to use operators like “<“ with this field. In specify7, that query flags with a red field, and returns a set of records that aren’t readable in the records window. It looks like it gets passed to the database, which returns the same number of records each time.
More serious, it won’t work with “=“ either. Screen shot:
The way the same field looks in 6 in the query:
