> Right now, while the database is still dialect 1, the high-precision

pseudo-numerics are still doubles. If you use the gfix way to change
the dialect without doing the intermediate step (with a dialect 2
client, as described in the original Migration Guide), you will never
know which is which.

>
> Please don't do it this way!

Yes, I know. I already followed the steps in the migration guide to
find out, where the problems are.
I just wanted to know if by any chance there is a way to find out
about the storage type via the database itself - not via migration
process.
So it's always like "according to the things I found out via
migration, this column should still be stored as double". And I can't
ask "are you really still stored as double". So if somebody would have
changed some column to exact storage without my knowledge (for what so
ever reason), I will never know!?

Thanks for clarification, Helen!

--Heiko