This is clearly a bug. I think one of the things that the next ODS need
to do is store char
length and byte length. If it is already doing this, then the engine
has a bug in it for not
checking both. If you are going to ignore the Char length, then lets
change SQL and
drop VARCHAR and CHAR and replace them with BYTECHAR.

If someone has relied on a bug in the engine, their problem.

Ann W. Harrison wrote:

>My guess is that we could put in a hack that changes the handling of
>user data in Unicode-FSS, but that the reaction will be strong and
>negative from people who've used it since InterBase 4 or 5 and count on
>the fact that their western European data actually averages about .8
>characters per byte. I know the next answer. We'll have a
>configuration parameter to allow or disallow overstuffed Unicode-FSS
>fields...
>
>Sounds of Ann running screaming out of the room, leaving hanks of
>torn-out hair in her trail...
>
>Cheers,
>
>
>Ann
>
>