| 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-2 Build 14156) Sat, 23 Dec 2023 15:05:47 +0000 |
| 2 |
> |
|
| 3 |
> |
1. IBUtils.FormatTimeZoneOffset A zero offset now includes a preceding '+' sign. |
| 4 |
> |
|
| 5 |
> |
2. TFBStatement.DoJournaling now exits immediately if journaling is not active. The |
| 6 |
> |
motivation for this is to avoid calling the Firebird API function 'getInfo' |
| 7 |
> |
unnecesarily. This function can return an error if an incompatible parameter type was |
| 8 |
> |
applied to the statement and hence can confuse resolving the bug. Note: a |
| 9 |
> |
specific case is in (e.g.) OpenCursorAtStart method when the array of const includes a |
| 10 |
> |
TDateTime. In this case, the param is set to a floating point type rather than |
| 11 |
> |
a Firebird datetime (array of const loses the distinction). |
| 12 |
> |
|
| 13 |
> |
3. TFBAttachment.SetParameters. if an attempt is made to set a parameter with a float |
| 14 |
> |
value, the metadata type is checked to see if the parameter is a Date/Time type. If so then |
| 15 |
> |
the value is assumed to be a TDateTime and the parameter is set using the AsDateTime |
| 16 |
> |
property. Otherwise, the value is assumed to be a floating point type and the AsDouble |
| 17 |
> |
property is used to set the property. This avoids the specific example given above. |
| 18 |
> |
|
| 19 |
> |
FBINTF Change Log version (1.4-1 Build 14103) Mon, 27 Nov 2023 14:26:35 +0000 |
| 20 |
|
|
| 21 |
|
1. FBSQLData: ensure that TResults.getSQLData and TResults.GetData use same error |
| 22 |
|
checks for range checking. |
| 23 |
|
|
| 24 |
+ |
2. FB25Client: In GetIBMessage, fb_interpret is now called multiple times such that |
| 25 |
+ |
any additional error information is decoded. |
| 26 |
+ |
|
| 27 |
+ |
3. FB25Statement: When changing a param type from Blob sub_type 1 to SQL_TEXT or SQL_VARYING |
| 28 |
+ |
charsetid is now preserved and size is set to default blob size. Now aligns with |
| 29 |
+ |
FB3 and later. |
| 30 |
+ |
|
| 31 |
+ |
4. DDL and DML string literals are now explicitly set to the connection character |
| 32 |
+ |
set rather than the default character set provided by the compiler. |
| 33 |
+ |
|
| 34 |
+ |
5. General tidy up of transliteration functions, now centralised in IBUtils. FPC testing |
| 35 |
+ |
now makes use of the RTL fpwidestring unit for support of international character |
| 36 |
+ |
sets. |
| 37 |
+ |
|
| 38 |
+ |
6. Database exception handling (see section 9.3 in user guide). |
| 39 |
+ |
* For FB3 and later API: Connection Character set now applied to message returned |
| 40 |
+ |
by fb_interpret and message then transliterated if necessary to the system character set. |
| 41 |
+ |
* For Legacy API: The message character set is guessed as UTF8 unless invalid |
| 42 |
+ |
UTF8 characters found when connection character set is assumed. Message then |
| 43 |
+ |
transliterated if necessary to system character set. |
| 44 |
+ |
Note: this difference of behaviour is because legacy API presents exception messages |
| 45 |
+ |
"as is", while FB3 server attempts to transliterate to connection character set. |
| 46 |
+ |
|
| 47 |
|
FBINTF Change Log version (1.4-0 Build 14011) Sat, 05 Aug 2023 11:09:09 +0100 |
| 48 |
|
|
| 49 |
|
1. Support package fbudr added for support of User Defined Routines (UDRs), and package |
