>
> It is a generally accepted design principle that you should
> not change a
> users data without warning, unless you apriori know what the
> form the data
> should be. Having a default condition to change data to my
> mind is I suggest
> counter intuitive. I appreciate the network bandwidth issue
> but if that is
> an issue and trimming will do no harm let the developer
> declare this by
> setting a "trim option".
>
> Example: Suppose an unusual encryption scheme allows right
> spaces in a CHAR
> field. A default position of trimming ruins it.
>

I agree. I had lots of trouble with Paradox, which also trimmed my spaces. I
used some simple crypting for storing passwords. In result the characters
were sometimes changed into space symbol. If they were last, then the
password didn't match.

So, please don't let database assume that it is smarter than programmer.


Riho-Rene Ellermaa
senior programmer
Hansabank