At 12:54 AM 03-08-02 +0000, you wrote:

>If I have an expression of:
> ... WHERE MyStoredTimestamp CONTAINING '08-03'
>It retrieves all Auguest 3 records and excludes all others. To
>me this implies that the engine is converting my text correctly
>to match my Timestamp, or more likely the engine is converting
>the timestamp to text.
>
>Similarly if I have a 32-bit integer the following expression works:
> ... WHERE MyInt CONTAINING '1'
>Will retrieve records, MyInt=
> 1, 10, 11, 12, ..., 21, 31, etc.
>This also makes it appear that the integer is being converted to
>a string and then a text comparison is being made.
>
>Are you implying that both of these should be invalid?

I guess what I'm saying is that if they have become invalid (or do so in
future) it would not be surprising, since those operators operate on strings.

Perhaps it would be closer to say that if you are getting implicit casting
"both ways" in such expressions, then consider it a bonus. In ODS 10,
there is a lot less implicit casting going on than there was in ODS 9. So
it might be wise to also consider it a warning that the EXTRACT() functions
accompanied the radical changes in date/time types with full ODS 10
(Dialect 3)...and to review your assumptions about implicit casts.

heLen

All for Open and Open for All
Firebird Open SQL Database · http://firebirdsql.org ·
http://users.tpg.com.au/helebor/
______________________________________________________________________