21.09.2015 12:33, Dimitry Sibiryakov wrote:
>> but presumably the xsqlda can carry them?
>
> Currently - not because XSQLVAR.sqllen is a signed short int.
And AFAIU nobody promised it could. "Cannot be assigned to anything but
a blob" includes the output message/parameter, i.e. such a literal
c
21.09.2015 9:30, Helen Borrie wrote:
> but presumably the xsqlda can carry them?
Currently - not because XSQLVAR.sqllen is a signed short int.
--
WBR, SD.
--
Firebird-Devel mailing list, web interface at
https://
At 06:59 p.m. 21/09/2015, Dmitry Yemanov wrote:
>21.09.2015 09:08, Simonov Denis wrote:
>
>>> 1. Can a string literal really be 64Kb if, internally, it is converted
>>> to varchar?
>
>Yes, it can. Internally our varchars allow strings up to 64KB, but this
>is not always respected in other layers,
21.09.2015 09:08, Simonov Denis wrote:
>> 1. Can a string literal really be 64Kb if, internally, it is converted
>> to varchar?
Yes, it can. Internally our varchars allow strings up to 64KB, but this
is not always respected in other layers, hence the official limit of
32KB (for the safety sake
Helen Borrie wrote Mon, 21 Sep 2015 08:31:36 +0300:
> Flagged as an improvement in RC1:
> core-4881 "Increase maximum string literal length to 64K (bytes) while
> setting a lower limit (of characters) for multibyte charsets based on
> their max char. length (UTF-8 literals will be limited to
Flagged as an improvement in RC1:
core-4881 "Increase maximum string literal length to 64K (bytes) while setting
a lower limit (of characters) for multibyte charsets based on their max char.
length (UTF-8 literals will be limited to 16383 characters)"
1. Can a string literal really be 64Kb if,
