[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [savannah-help-public] [sr #109423] Non-BMP characters truncate comm
From: |
Ineiev |
Subject: |
Re: [savannah-help-public] [sr #109423] Non-BMP characters truncate comments |
Date: |
Tue, 12 Dec 2017 07:40:15 -0500 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Tue, Dec 12, 2017 at 12:30:42AM -0700, Bob Proulx wrote:
> Ineiev wrote:
> > The question is what to do. we could wait for MySQL or store new messages
> > in something like base64, with a magic prefix.
>
> Upgrading quickly is problematic. And trying to upgrade just the
> database system and not the clients is also problematic. Or perhaps
> the reverse if that is the problem. At least not without testing. In
> another set of systems I tried upgrading just half of things and then
> the clients and server were out of sync with options they were trying
> to pass. It caused a lot of problems.
>
> How much of a problem is this?
Some characters break the comment they are in.
> Can we scan the data before storing it
> and detect when we will have the problem and then encode it then?
Probably we could. I think some UTF-8 parsing would be needed, it's
somewhat harder than to encode unconditionally.
signature.asc
Description: Digital signature