This issue also occurs with folow PHP versions (for any collate - UTF8)
PHP 7.0.12+
PHP 7.1.0 RC4+
Firebir 2.5.5 + and Firebird-3.0.1.32609_0_x64
I have no test with other versions.
The driver could map the SQLVARs of SQL_TEXT to SQL_VARYING and adjust
offsets and lengths?
Or else it has to do
On 22/11/16 12:58, Delmar Wichnieski wrote:
> Since there was no answer here on the list, I was feeling alone and afraid
> and wondering why no one else has this problem.
Delmar I must apologise as I HAD posted a reply, but it did not actually
go through ... list in bounce emails mode which I
Hi Delmar,
> -Original Message-
> From: Delmar Wichnieski [mailto:delmar.del...@gmail.com]
> Sent: Tuesday, November 22, 2016 12:27 PM
> To: php-wind...@lists.php.net; php-db@lists.php.net
> Subject: [PHP-WIN] Re: CHAR field with charset UTF8 and COLLATION
> UNICODE_CI_AI or UTF8 PHP is
For 30 days, I avoided opening as a bug, because I researched a lot, I
asked in some forums with more than 50 thousand users and I did not find
anyone else with this problem, so much so that in the initial post, I asked
if it could be a configuration problem, or bug or lack of full UFT8 support
But VARCHAR fields work correctly. Problem only in CHAR.
And it should not be gambol, because
"Each UTF is reversible, thus every UTF supports lossless round tripping:
mapping from any Unicode coded character sequence S to a sequence of bytes
and back will produce S again."
Source
On 22.11.2016 at 12:27, Delmar Wichnieski wrote:
> This issue also occurs with folow PHP versions (for any collate - UTF8)
> PHP 7.0.12+
> PHP 7.1.0 RC4+
> Firebir 2.5.5 + and Firebird-3.0.1.32609_0_x64
> I have no test with other versions.
>
>
> The driver could map the SQLVARs of SQL_TEXT to
On 22/11/16 18:01, Delmar Wichnieski wrote:
> 2016-11-22 12:42 GMT-02:00 Lester Caine :
>
>> > needs help to move
>> > the string to a variable that it can check if the UTF8 data is a single
>> > character or multiple characters.
>> >
>> >
> I believe it is a single byte, the
On 22/11/16 13:56, Delmar Wichnieski wrote:
> But VARCHAR fields work correctly. Problem only in CHAR.
VARCHAR is trimmed to the number of bytes used ... not the number of
'characters'! CHAR is only designed for single byte characters IN PHP so
providing multi byte characters to a CHAR(1) field
2016-11-22 12:42 GMT-02:00 Lester Caine :
> needs help to move
> the string to a variable that it can check if the UTF8 data is a single
> character or multiple characters.
>
>
I believe it is a single byte, the goal is to simulate a boolean field,
where I only use S for yes