Chad Z. Hower wrote:

> :: The change has been done during the development of FB 2.0.
> :: It hasn't been backported to FB 1.5. So, you'll see this
> :: change in FB 2.0, when it comes out.
>
> Ok - so to recap - it is fixed in 2.0? VarChar(80) now actually means 80
> chars?

If you use the new character set UTF8. Old character sets (UNICODE_FSS)
will continue to have the old behavior. Which by the was is not
uncommon in other databases - MySQL certainly behaves that way.

Regards,


Ann