| 1 |
< |
FBINTF Change Log version (1.4-1 Build 14096) Sat, 21 Oct 2023 14:41:26 +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. |
