1 |
< |
FBINTF Change Log version (1.4-1 Build 14019) Sat, 05 Aug 2023 13:21:51 +0100 |
1 |
> |
FBINTF Change Log version (1.4-1 Build 14083) Fri, 20 Oct 2023 11:41:24 +0100 |
2 |
|
|
3 |
|
1. FBSQLData: ensure that TResults.getSQLData and TResults.GetData use same error |
4 |
|
checks for range checking. |
5 |
|
|
6 |
+ |
2. FB25Client: In GetIBMessage, fb_interpret is now called multiple times such that |
7 |
+ |
any additional error information is decoded. |
8 |
+ |
|
9 |
+ |
3. FB25Statement: When changing a param type from Blob sub_type 1 to SQL_TEXT or SQL_VARYING |
10 |
+ |
charsetid is now preserved and size is set to default blob size. Now aligns with |
11 |
+ |
FB3 and later. |
12 |
+ |
|
13 |
+ |
4. DDL and DML string literals are now explicitly set to the connection character |
14 |
+ |
set rather than the default character set provided by the compiler. |
15 |
+ |
|
16 |
+ |
5. General tidy up of transliteration functions, now centralised in IBUtils. FPC testing |
17 |
+ |
now makes use of the RTL fpwidestring unit for support of international character |
18 |
+ |
sets. |
19 |
+ |
|
20 |
+ |
6. Database exception handling (see section 9.3 in user guide). |
21 |
+ |
* For FB3 and later API: Connection Character set now applied to message returned |
22 |
+ |
by fb_interpret and message then transliterated if necessary to the system character set. |
23 |
+ |
* For Legacy API: The message character set is guessed as UTF8 unless invalid |
24 |
+ |
UTF8 characters found when connection character set is assumed. Message then |
25 |
+ |
transliterated if necessary to system character set. |
26 |
+ |
Note: this difference of behaviour is because legacy API presents exception messages |
27 |
+ |
"as is", while FB3 server attempts to transliterate to connection character set. |
28 |
+ |
|
29 |
|
FBINTF Change Log version (1.4-0 Build 14011) Sat, 05 Aug 2023 11:09:09 +0100 |
30 |
|
|
31 |
|
1. Support package fbudr added for support of User Defined Routines (UDRs), and package |