Lately, I've run into a few problems with FLOAT type fields on FB
1.02:
- Error with indexing and some 0-values (everything works fine
without an index, but order is wrong *with* index)
- Error when inserting from a FLOAT field to a DOUBLE PRECISION
column ("truncation error", etc.)

Now, I wonder if FLOAT type is not regarded "safe" anymore ?
FLOAT is desireable in my application beacuse of row width / database
size. When you have millions of rows and 30 float fields, it really
makes a difference. But is there some issue about FB's FLOAT type
support that I should know ?

Regards,

Bjørge