Re: 1 cset was pushed to core/stable: get rid of single spaces in query result...

In article <[email protected]>, "Jason Judge" <[email protected]> 
wrote:
>Heh - it is difficult convincing the PHP devs that this *is* a bug. While
>CHAR columns can never be empty (zero-length), VARCHAR columns certainly
>can. I think we need to tread carefully here, and checking specifically for
>a single space, as you have done (rather than trimming strings as PHP used
>tgo do), is a good solution, IMO.
>
>Of course, the bug may be further upstream in the database drivers, outside
>the control of PHP, but the devs never explain whether that is the case.
>
>-- JJ
>
Yeah, it's a nasty thing, that single space in mssql drivers. I started adding
some trimming here & there in the Xaraya code to work around the issue,
but since I found more and more places where empty strings are supposed
to be ... empty, I decided to attack the problem at its source, i.e. the mssql
driver :-)

Another way that I experimented with was to "force" SQL Server to work
in compatibility level 80 from the start, but that didn't really work out
in practice...

Mike.