|
|
Posted by Rik Wasmus on 10/01/97 12:00
On Tue, 15 Jan 2008 18:26:12 +0100, Good Man <heyho@letsgo.com> wrote:
> "Rik Wasmus" <luiheidsgoeroe@hotmail.com> wrote in
> news:op.t4zeklpi5bnjuv@metallium.lan:
>
>> On Tue, 15 Jan 2008 18:06:21 +0100, Good Man <heyho@letsgo.com> wrote:
>>>> Of course, my real problem is how the whitespace gets in there in
>>>> the first place.
>>>
>>> Nope, who cares how it got in?
>>
>> Euhm, if I request a form editing some record, and I change one field,
>> I don't expect to get an 'invalid' error on another in my view
>> unaltered field. In this case, we KNOW whitespace is invalid, and
>> will trim() it out. However, if whitespace is valid, this could stack
>> whitespace on the end for every edit action. Not something you'd
>> like.
>
> true, i wasn't even imagining it being created on the
> back-end/server-side.
The OP didn't mention it indeed. I assumed it because the zip code field
apparantly was filled with a $row['zip'] variable, which makes one
immediately think of a fetched row from a database result.
--
Rik Wasmus
Navigation:
[Reply to this message]
|