Terry Steyaert wrote:
>
> <Orignal cut for band-width sake.>
>
> Overall, we have always had problems during selects based upon
> strings. Our ultimate fix, from Oracle 6 on, has been to space fill
> the strings to a set length. This seems to clean up the problems that
> we have had doing exactly what you are doing. If your database column
> is filled to 20 characters, and your string is filled to the 20
> characters, it will work fine. If they are not, it generally doesn't
> work.
>
> If you can manage it, do your selects based upon integer or number
> columns as they are much more reliable than strings. With our space
> fills, I don't get the errors that you are seeing, but before we space
> filled, occationally strange errors would occur.
That is a kluge work-around and shouldn't be used. This type of code is
typically used when programmers don't read the documentation and don't
understand the difference between CHAR and VARCHAR data and the differences
between versions prior to 7.0 and subsequent versions. Kluge code will
eventually cause problems down the road. The proper way is to write PRO-C
code according to the way it is supposed to be used.
Received on Fri Mar 24 2000 - 09:41:09 CST
