2017. 12. 19. 21:13 keltezéssel, setysvar setys...@gmail.com
[firebird-support] írta:
> Why would you want collate AFTER containing? I must admit I haven't
> tried your queries in Fb 3.0 (I'm still on 2.5), but I'd say the
> sensible way to specify what you want, would be
>
> SELECT * FROM
>After the original "Problem with CONTAINING and COLLATE" thread I
switched to UTF8 but not happy with it.
>The optional COLLATE after CONTAINING have no effect, the database
default COLLATION used. See the below
>examples. Tried with 3.0.3.32854 snapshot and Linux 64bit (Ubuntu
14.04.1).
Hi All,
After the original "Problem with CONTAINING and COLLATE" thread I
switched to UTF8 but not happy with it. The optional COLLATE after
CONTAINING have no effect, the database default COLLATION used. See the
below examples. Tried with 3.0.3.32854 snapshot and Linux 64bit (Ubuntu
08.12.2017 12:07, Mark Rotteveel m...@lawinegevaar.nl [firebird-support] wrote:
> It should return no results. If it can't transliterate, it means that
> the character definitely does not exist in the target column, so the
> comparison is false.
When character is transliterated into charset
On 2017-12-08 12:01, Dimitry Sibiryakov s...@ibphoenix.com
[firebird-support] wrote:
> 08.12.2017 11:56, Mark Rotteveel m...@lawinegevaar.nl
> [firebird-support] wrote:
>> I don't agree with this. The string literal is in the connection
>> character set, but the value should be converted to the
08.12.2017 11:56, Mark Rotteveel m...@lawinegevaar.nl [firebird-support] wrote:
> I don't agree with this. The string literal is in the connection
> character set, but the value should be converted to the target character
> set (of the column) for the comparison
No. Imagine connection charset
On 2017-12-07 19:06, Dimitry Sibiryakov s...@ibphoenix.com
[firebird-support] wrote:
> 07.12.2017 18:46, Gabor Boros mlngl...@bgss.hu [firebird-support]
> wrote:
>> Why does the connection charset count?
>
>Because you are sending queries in connection charset. And string
> literals in them
07.12.2017 18:46, Gabor Boros mlngl...@bgss.hu [firebird-support] wrote:
> Why does the connection charset count?
Because you are sending queries in connection charset. And string literals
in them are
in connection charset. Because of that your 'x' cannot have COLLATE PXW_HUNDC.
--
Hi All,
I have a database with DEFAULT CHARACTER SET WIN1250 COLLATION PXW_HUN
and a table in it:
CREATE TABLE TABLE_1 (NEV VARCHAR(60) CHARACTER SET WIN1250 COLLATE
PXW_HUN);
Connect with ISQL:
isql 1.2.3.4:MYDB -charset UTF8 -user myadmin -password mypasswd
Execute this:
SELECT * FROM
