| 1 |
< |
FBINTF Change Log version (1.1-4) Sat, 08 Dec 2018 11:11:20 +0000 |
| 1 |
> |
FBINTF Change Log version (1.1-6 Build 12344) Fri, 21 Aug 2020 15:15:24 +0100 |
| 2 |
> |
|
| 3 |
> |
1. GetImplementationVersion now correctly returns '3.0' for Firebird 3 API |
| 4 |
> |
with a Firebrid 3 client library. |
| 5 |
> |
|
| 6 |
> |
2. Linux Only: FIREBIRD environment variable is now checked when loading the client library. |
| 7 |
> |
If a client library path is not explicitly provided and the FIREBIRD environment |
| 8 |
> |
variable is set then the directory given by this variable and any 'lib' subdirectory |
| 9 |
> |
are searched for the Firebird client library. Only if none is found, is the default |
| 10 |
> |
client library used. |
| 11 |
> |
|
| 12 |
> |
3. IUtil.FormatStatus now used to format error messages when using new API |
| 13 |
> |
|
| 14 |
> |
4. Fixed Array SDL: array_desc_scale now correctly encoded as a signed integer. |
| 15 |
> |
|
| 16 |
> |
5. SQL_TEXT handling changed. When the value of an SQL_TEXT (i.e. fixed width string) column is |
| 17 |
> |
returned using GetAsString and the string codepage is UTF8, the string is truncated so |
| 18 |
> |
that the byte length corresponds to the number of characters specified for the column. |
| 19 |
> |
SQL_TEXT strings are no longer automatically trimmed to remove all trailing white space. This is |
| 20 |
> |
correct behaviour but may affect some implementations that relied upon automatic |
| 21 |
> |
trimming of trailing white space. |
| 22 |
> |
|
| 23 |
> |
6. New IFirebirdAPI Calls: |
| 24 |
> |
function GetClientMajor: integer; |
| 25 |
> |
function GetClientMinor: integer; |
| 26 |
> |
|
| 27 |
> |
7. IColumnMetaData and IArrayMetaData: new method |
| 28 |
> |
function GetCharSetWidth: integer; |
| 29 |
> |
|
| 30 |
> |
|
| 31 |
> |
FBINTF Change Log version (1.1-5 Build 12044) Fri, 17 Apr 2020 12:30:01 +0100 |
| 32 |
> |
|
| 33 |
> |
1. ISQLParams.GetHasCaseSensitiveParams added. Returns true if param names are |
| 34 |
> |
case sensitive |
| 35 |
> |
|
| 36 |
> |
2. Single line SQL comments starting with '--' are now recognised by SQL Parser. |
| 37 |
> |
|
| 38 |
> |
3. New API Calls: |
| 39 |
> |
IColumnMetaData.GetStatement |
| 40 |
> |
IColumnMetaData.GetTransaction |
| 41 |
> |
ISQLData.GetStrLength |
| 42 |
> |
IResults.GetStatement |
| 43 |
> |
IAttachment.OpenBlob (using Blob metadata) |
| 44 |
> |
IAttachment.OpenArray (using array metadata) |
| 45 |
> |
|
| 46 |
> |
4. FBMessages: removal of unused messages |
| 47 |
> |
|
| 48 |
> |
5. TFBArray.Create (2nd case): ensure that FFirebirdClientAPI is correctly set. |
| 49 |
> |
|
| 50 |
> |
6. TIBSQLStatementType: SQLSavePoint added to end of enumeration. |
| 51 |
> |
|
| 52 |
> |
FBINTF Change Log version (1.1-4 Build 11515) Fri, 28 Dec 2018 10:04:19 +0000 |
| 53 |
|
|
| 54 |
|
1. Fix a problem with the SQL parameter parser that failed to recognise parameters |
| 55 |
|
where the second character of the parameter name is a numeric. |
| 56 |
|
|
| 57 |
+ |
2. New method for IAttachment: procedure getFBVersion(version: TStrings); |
| 58 |
+ |
This returns the isc_version connection information as one or more lines. |
| 59 |
+ |
This is the same information as returned by isql with the -z option. |
| 60 |
+ |
|
| 61 |
+ |
3. If -dFIREBIRD3APIONLY is used as a compiler option then the legacy Firebird API |
| 62 |
+ |
is no longer compiled in. Likewise, if -dLEGACYFIREBIRDAPIONLY is used as a |
| 63 |
+ |
compiler option then the Firebird 3 API is no longer compiled in. |
| 64 |
+ |
|
| 65 |
+ |
4. IColumnMetaData: new method. |
| 66 |
+ |
|
| 67 |
+ |
TIBDateTimeFormats = (dfTimestamp, {SQL TIMESTAMP} |
| 68 |
+ |
dfDateTime, {SQL DATETIME} |
| 69 |
+ |
dfTime); |
| 70 |
+ |
|
| 71 |
+ |
function GetDateTimeStrLength(DateTimeFormat: TIBDateTimeFormats): integer; |
| 72 |
+ |
|
| 73 |
+ |
This returns the max. number of characters returned by the "AsString" method |
| 74 |
+ |
when the SQL type of the column is respectively TIMESTAMP, DATETIME or TIME. |
| 75 |
+ |
|
| 76 |
+ |
5. Additional argument for IAttachment.PrepareWithNamedParameters - |
| 77 |
+ |
CaseSensitiveParams: boolean = false |
| 78 |
+ |
|
| 79 |
+ |
If this argument is set to true then SQL parameter names are assumed to be case |
| 80 |
+ |
sensitive and must be referenced (using ISQLParams.ByName) using the case |
| 81 |
+ |
sensitive name. |
| 82 |
+ |
|
| 83 |
+ |
6. Bug fix: when setting a query parameter, it is now possible, when the parameter |
| 84 |
+ |
is of type VarChar or Char to set the parameter to a numeric value (e.g. using |
| 85 |
+ |
.AsCurrency) and then subsequently to update the value to a non-numeric string |
| 86 |
+ |
using .AsString. |
| 87 |
+ |
|
| 88 |
+ |
|
| 89 |
|
|
| 90 |
|
FBINTF Change Log version (1.1-3) Wed, 05 Dec 2018 14:28:10 +0000 |
| 91 |
|
|
