Dmitry Kovalenko

Incorrect result type of COALESCE and pair (INTEGER, NUMERIC(6,1))

5

ISQL Version: WI-V3.0.8.33506 Firebird 3.0 SQL> create table TTT4(COL_INTEGER INTEGER, COL_NUM_6_1 NUMERIC(6,1)); SQL> insert into TTT4 (COL_INTEGER, COL_NUM_6_1) values (2147483647,12345.6); SQL> select COALESCE(COL_INTEGER,COL_NUM_6_1) from TTT4; **Result** > COALESCE > ============...

[FB4] An improved support of UDF SCALAR_ARRAY-arguments

5

Hello. It is the implementation of the second solution to issue #7843. These changes force a server to do two things: 1. Generation of names for INPUT-arguments of UDF and...

Hello. Remote protocol 13 (FB3+) allows to operate with 32bit number of buffer sizes. To say more exactly, the maximum size of data can be up to 0xFFFF0000-1 bytes. It...

Server can't load zlib1.dll again after first failure

1

Hello 1. rename zlib1.dll in server folder to "zlib1.dll----" 2. try to connect with using wire_compression 3. server returns the error 4. restore zlib1.dll name 5. try to connect with...

[UDF] Server must prevent "return BY VALUE" for data types ISC_TIMESTAMP_TZ, ISC_TIME_TZ and so on

3

Firebird prohibits the creation of UDF with "return BY VALUE" for data types ISC_TIMESTAMP, ISC_QUAD based on structs but allows it for: - FB_I128_t - FB_DEC34_t - FB_DEC16_t - ISC_TIMESTAMP_TZ...

It is a fix of problem #7892 1. The creation of scalar_array_desc was corrected 2. The calculation of Function::fun_temp_length was corrected

Hello, sizeof(scalar_array_desc) == 32 Note - it is a size of an array descriptor with one dimension. When I call the UDF ``` sql DECLARE EXTERNAL FUNCTION IBP_UDF__ADIM__I4 INTEGER BY...

It is a fix for issue #7883. Test SQLs: ``` sql DECLARE EXTERNAL FUNCTION UDF_DUMMY6__3 RETURNS INT128 BY VALUE ENTRY_POINT 'IB_UDF_abs' MODULE_NAME 'ib_udf'; DECLARE EXTERNAL FUNCTION UDF_DUMMY6__3 RETURNS NUMERIC(19,0) BY...

These changes force a server to return correct datatype for CAST(something as array datatype) - array type instead type of element. 1) Test of CAST(arrayColumn as ARRAY) ``` SQL> set...

`CREATE TABLE TEST_ARR1 (COL_I4 INTEGER[0:2]);` -- insert array [1,2,3] (through API) `INSERT INTO TEST_ARR1 (COL_I4) VALUES (?);` --- result is OK. `SELECT COL_I4 FROM TEST_ARR1;` -- **Bad column type**: VARCHAR...