14.08.2020 15:36, Mark Rotteveel wrote:
b) Any character other than a in the character set identified by the set specification> or implied by “N”.
"""
Which also confirms that the current Firebird behaviour is correct.
Unfortunately that's right.
That is simple to achieve: **don't use intr
On 14-08-2020 14:21, Dimitry Sibiryakov wrote:
14.08.2020 13:56, Mark Rotteveel wrote:
b) Otherwise, there shall be no between the
and the , and the set of characters
contained in the shall be wholly contained
in the character set specified by the .
a) If the specifies a specification>,
14.08.2020 13:56, Mark Rotteveel wrote:
b) Otherwise, there shall be no between the and the set specification>, and the set of characters contained in the
shall be wholly contained in the character set specified by the specification>.
a) If the specifies a , then the character set specified
On 14-08-2020 13:09, Dimitry Sibiryakov wrote:
Hello All.
What SQL standard is telling about charset introducers (such as
"_utf8 'abc'")?
From my knowledge it can be interpreted in two ways:
1) Following byte sequence has given charset.
2) Following character sequence must be used a
Hello All.
What SQL standard is telling about charset introducers (such as "_utf8
'abc'")?
From my knowledge it can be interpreted in two ways:
1) Following byte sequence has given charset.
2) Following character sequence must be used as a string in given charset.
First option resuts
