20.01.2021 15:43, Adriano dos Santos Fernandes wrote:
On 20/01/2021 10:03, Alex Peshkoff via Firebird-devel wrote:
I suppose VARCHAR(63) CHARACTER SET ASCII is OK.
I agree.
Seems, we have agreement, very well.
Thanks all,
Vlad
Firebird-Devel mailing list, web interface at
On 20/01/2021 10:03, Alex Peshkoff via Firebird-devel wrote:
>
> I suppose VARCHAR(63) CHARACTER SET ASCII is OK.
>
I agree.
Adriano
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
20.01.2021 16:03, Dimitry Sibiryakov wrote:
I agree that config parameters hardly can be not in ASCII but I
cannot imagine them to be longer that 10-20 characters. It would be very
hard to type such long settings without errors and my imagination is not
enough to suggest a meaningful name of
20.01.2021 13:41, Vlad Khorsun wrote:
Today we discussed these reasons with Dmitry and agreed that it is not very
convincing.
For example, we have no intention to have non-ASCII names of settings in
firebird.conf
and 63 characters could be not enough at some day.
I agree that config
On 1/20/21 3:41 PM, Vlad Khorsun wrote:
Hi, all
I'll speak about new table RDB$CONFIG introduced with implementation
of CORE-3708.
The field RDB$CONFIG_NAME has datatype defined as VARCHAR(63)
CHARACTER SET UTF8.
The original reasons behind this choice was:
- UTF8 as charset for most
Hi, all
I'll speak about new table RDB$CONFIG introduced with implementation of
CORE-3708.
The field RDB$CONFIG_NAME has datatype defined as VARCHAR(63) CHARACTER SET
UTF8.
The original reasons behind this choice was:
- UTF8 as charset for most system defined fields,
- VARCHAR(63) to
