What's New in InterBase 2017 Update 3
Go Up to Main Page
InterBase 2017 Update 3 includes new features and bug fixes.
See the following sections for more information:
There are no new features on this release.
Note: Starting with InterBase 2017 Update 3 there is a single unified installer for both English and Japanese.
Please refer to this section for more information.
Order of prepared parameters
In a parameterized query, the order of parameters received for an Input SQLDA has been fixed. The fixed order is now both intuitive and in "visible order" as per ANSI/SQL standard requirements. This is useful especially when parameters are used in the main query's conjuncts (
WHERE conditions), and in the query's column-list which have one or more sub-query(s) themselves with parameters in them.
The client API,
isc_dsql_describe_bind(), now correctly returns the visual order sequence number for each parameter in the input SQLDA and uses it internally to transform the user provided SQLVARs to InterBase engine expected order. The changes are only available for SQLDA version >= 2.
A new example,
api17.c, has been provided to showcase how this works.
The sample below showcases how named parameters are used in IBX and FireDAC components. The named parameters should work for both
:NO in that parameter order. The client component is expected to provide values in the SQLVAR array in the visible order of
:TEST followed by
select P.emp_no, P.first_name, P.last_name, (select 1 from RDB$DATABASE where 1 <> :TEST) from employee P where P.emp_no = :NO
New IBConfig parameter
This parameter allows you to manipulate the number of pages to be prefetched. This parameter should be left on its default status and changed only for testing purposes when it is suspected to produce performance issues. You can find more information Here.
New IBConfig parameter
This parameter allows you to enable/disable the use of partial index selectivity data for SQL query optimization. This parameter should be left on its default status and changed only for testing purposes when it is suspected to produce performance issues. You can find more information Here.
Change View Performance
In InterBase 2017 Change View retrieval performance has been enhanced.
Note: This performance enhancement only works on ODS 17 databases.
First Sweep of a Restored Database is now a Fast Sweep
With InterBase 2017, any database that you restore is immediately marked as swept, therefore the first sweep of that database is a fast sweep. In order to take advantage of this feature, you need to perform a database restore with InterBase 2017 and use either ODS 15 or ODS 16. See Sweep Interval and Automated Housekeeping for more information about sweeping.
See Resolved Defects for a list of bug fixes in InterBase 2017 Update 3.
For system requirements to install and run InterBase, see System Requirements/Prerequisites.