From: | "Eugene E(dot)" <sad(at)bankir(dot)ru> |
---|---|
To: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: have you feel anything when you read this ? |
Date: | 2006-03-21 10:36:20 |
Message-ID: | 441FD724.8050802@bankir.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Scott Marlowe wrote:
> On Mon, 2006-03-20 at 02:06, Eugene E. wrote:
>
>>http://dev.mysql.com/doc/refman/5.0/en/news-5-0-19.html
>>--- cut ---
>>mysql no longer terminates data value display when it encounters a NUL
>>byte. Instead, it displays NUL bytes as spaces. (Bug #16859)
>>--- cut ---
>
>
> Everyone here realizes that this is a mysql CLIENT bug, not server side.
>
> i.e. if you're writing an application and request that binary text
> string, you'll get it with nuls in it, just like you put in.
>
> Now, I'm not sure that turning nulls into spaces is the best way to
> handle this in the client. In fact, I'm sure it's not. But this is not
> a server bug, it's a client bug.
I was not sure about MySQL, thank you for your explaination.
This ensures me that even MySQL server handles NUL-bytes properly
regardless to client problems.
From | Date | Subject | |
---|---|---|---|
Next Message | Alexis Paul Bertolini | 2006-03-21 13:02:30 | Job queue, how would you implement this? |
Previous Message | Eugene E. | 2006-03-21 10:33:25 | Re: have you feel anything when you read this ? |