Updated: September, 2011
This file contains important information that may not appear in the online Help. Please read this file in its entirety.
The readme covers the following sections:
For system requirements to install and run InterBase XE, please refer to the Installation, Registration, and Licensing Information document.
The document set in PDF format requires about 13MB of space on your disk. The documents install by default when Client and Server or Client is chosen during the InterBase install process. However, in a custom install, it is possible to choose an install that does not include the document set. If you want to install documents at a later time, run the InterBase install, choose Custom, and select the documentation.
You can also copy them from the Documentation directory of the InterBase CD-ROM or download file. Detailed command-line and step-by-step instructions are provided for most topics. Where applicable, instructions are also provided on how to perform a task or use a feature using IBConsole, the InterBase user interface. The following table displays each user guide and a description of the topics covered.
| Guide Name | Description of Topics Covered |
| Operations Guide |
How-to information on working with InterBase databases. Topics include:
|
| Data Definition Guide |
How-to information on designing and building InterBase databases. Topics include:
|
| Developer's Guide |
How-to information on developing InterBase database applications using Embarcadero development tools, JDBC, and ODBC. Topics include:
|
| API Guide | How-to information on developing InterBase applications using the InterBase API interface. Topics include:
|
| Embedded SQL Guide |
How-to information on developing InterBase applications using embedded SQL. Topics include:
|
| Language Reference Guide | This is a reference guide to InterBase elements. Topics include:
|
| Setup.html | This document provides detailed installation and registration instructions for all platforms. |
There are several new features available for this release:
Listed below are the new features from previous releases:
If you are using OTW SSL TCP/IP connection:
For the Update 3 release you no longer need to specify your server hostname by the IBSSL_SERVER_HOST_NAME parameter in
If you do specify the hostname in the ibss_config file, you must ensure that the hostname resolves to IPv4 TCP/IP address and not a IPv6 address. One way to force a IPv4 resolution is to include your hostname in the hosts file with a valid IPv4 address. On Windows your hostname should be in the <Windows system file>\drivers\etc\hosts file.
The ODBC Drivers for InterBase XE Windows, Linux, and Solaris have been upgraded.
The link for the ODBC Windows driver is:
http://cc.embarcadero.com/item/25658/
The link for the ODBC Linux driver is:
http://cc.embarcadero.com/item/25139/
The link for the ODBC Solaris driver is:
http://cc.embarcadero.com/item/25660/
Databases with AES encryption keys allow backup/restore activities only as a service. It was designed to facilitate discovering a "strong encryption" license mandate in the engine. Databases with DES encryption keys are allowed to be backed up (and restored) as a pure client. However, the encrypted data, now decrypted with proper authentication, could be visible in transit in the process space of GBAK (or other backup applications).
Backup/restore operations can now be restricted on any encrypted database, whether DES or AES strength. An error message now displays the following when GBAK is not run as a service on encrypted databases:
gbak: ERROR: encrypted database: use -service switch
InterBase XE Update 2 has upgraded from 1.0.0a to OpenSSL 1.0.0d.
For more information on using OpenSSL in InterBase XE, please reference Network Configuration in the Operations Guide, as well as Encrypting your Data in the Data Definition Guide.
For additional information on OpenSSL please refer to: http://openssl.org/
The direct Input/Output (I/O) capability makes InterBase more scalable with very large databases on systems where there are memory resource limitations. With the Update 2 release, InterBase enables this "direct I/O" functionality on Windows OS. This functionality circumvents the issue observed by many on Windows 2008 R2 and Windows 7 64-bit OS editions where System File Cache uses up too much physical memory leading to sluggish system performance.
Issue: InterBase uses buffered file I/O on all platforms to perform I/O on database pages for the file on disk. The pages are delivered via the System File Cache, which acts as a duplicate store of the pages on RAM. Subsequent loads of the same page(s) will be quickly served by the OS kernel if the page exists in the System File Cache. On systems where there is high contention with other files for the System File Cache (a shared pool used by all processes for buffered file I/O) the performance of InterBase may not be optimal. If available System File Cache is limited due to RAM resource limitations, the kernel must spend time cleaning up unused blocks of memory from other processes as well as provide for servicing a new block I/O request.
Solution: The performance problem is alleviated by using "direct I/O" (also known as non-buffered I/O) so blocks of pages are directly read from the disk into the process space and do not need to use the System File Cache.
# gfix {-write {async, sync, direct}] . . .
For example:
#gfix -write direct foo.ib -user sysdba -password masterkey
# gbak [-write {async, sync, direct}] . . .
For example:
# gbak -write direct -r foo.ibk foo.ib -user sysdba -password masterkey
Argument: isc_spb_res_write_mode
Purpose: Set the write mode of the database. The next byte must be one of:
isc_spb_res_wm_async
Corresponds to gbak-write
isc_spb_res_wm_sync
isc_spb_res_wm_direct
Argument Length: 1 byte
Argument Value: byte
Add isc_spb_prp_wm_direct to the following argument:
isc_spb_prp_write_mode
&# gstat -h foo.ib -user sysdba -password masterkey . . . Database header page information: Flags 0 Checksum 12345 Write timestamp Mar 3, 2011 13:36:31 Page size 8192 ODS version 15.0 . . . Creation date Feb 23, 2011 14:58:27 Attributes force write, direct, no reserve Variable header data: Sweep interval: 20000 *END* . . .
feature is not supported -direct I/O operation
direct" I/O setting on a database is only possible if the database page size is an exact multiple of the file's underlying disk sector size. The standard for so many decades has been 512 bytes per sector on hard disks. Newer hard disks however are trying to adopt the more Advanced Format of 4096 bytes per sector.
InterBase supports the following database page sizes: 1024, 2048, 4096, 8192 and 16384 bytes per page. Databases that have a page size of 1024 or 2048 bytes cannot be set to "direct" I/O on hard disks that only support the 4096 bytes per sector standard; you need to restore your database to a larger page size on such disks before enabling "direct" I/O on them.
If you try to enable "direct" I/O on an incompatible device, the following error message is returned stating the minimum required database page size. The following example shows an error message where the disk sector size is 4096 bytes.
Error: Must backup and restore to DB page size >= 4096 bytes to support direct I/O on this device.
The ib_install.exe is delivered with the 32-bit Edition issue. You will need to run this installer if you want to to use the 32-bit Edition on Windows.
The topics below cover the critical information you need to implement the 64-bit application.
The following table displays the new client library names for the 64-bit DLL's.
| Library Name | Location | Notes |
| ibclient64.dll | <interbase>/bin | This is a new InterBase client DLL for native 64-bit applications. It is being used by 64-bit InterBase command-line tools currently, and will need to be deployed with 64-bit applications built by customers (in place of gds32.dll which is for the 32-bit target). |
| ibxml64.dll | <interbase>/bin | This is a new InterBase XML DLL for native 64-bit applications. It will need to be deployed with 64-bit applications built by customers (in place of ibxml.dll which is for the 32-bit target) if they are using the InterBase XML api. |
| ib_util64.dll | <interbase>/bin | This is a new InterBase UTILS DLL for native 64-bit applications. It will need to be deployed with 64-bit applications built by customers (in place of ib_util.dll which is for the 32-bit target). |
| ibclient64_ms.lib | <interbase>/SDK/lib_ms | Import library for building 64-bit applications targeting the ibclient64.dll. |
| ibxml64_ms.lib | <interbase>/SDK/lib_ms | Import library for building 64-bit applications targeting the ibxml64.dll. |
| ib_util64_ms.lib | <interbase>/SDK/lib_ms | Import library for building 64-bit applications targeting the ib_util64.dll. |
New interfaces have been implemented which support the following:
| JDBC Name | InterClient Name | Exceptions/Comments |
| java.sql.Blob | interbase.interclient.Blob |
For all API the parameter pos is ignored and assumed to be 1, hence the complete BLOB is returned. For example in the method OutputStream setBinaryStream(long pos) the parameter pos is ignored. The same is true for all other methods which take the "pos" parameter. public long position(byte[] pattern, long start) and public long position (java.sql.Blob blob, long start) are not supported. |
| java.sql.Clob | interbase.interclient.Clob | |
| java.io.inputStream | interbase.interclient IBBlobInputStream |
Special implementation of the java.io.inputStream for InterBase Blob (and Clobs). Use the read() methods from this stream to access the underlying data. |
The following methods have been implemented in this release:
This release implements stronger password protection on InterBase databases to comply with password requirements from the Payment Card Industry - Data Security Standard (PCI DSS). This additional functionality supports a longer effective password length, resulting in stronger password protection.
The DES-CRYPT password algorithm has been replaced with a modern cryptographic hash function that is more widely accepted by organizations in private industry and government. The design uses SHA-1, which generates a fixed length 160-bit hash.
isql admin.ib -user SYSDBA -pass xxxxxxx sql> ALTER DATABASE SET PASSWORD DIGEST 'SHA-1'; sql> CREATE DOMAIN PASSWORD_DIGEST AS VARCHAR(16) CHARACTER SET ASCII; sql> ALTER TABLE USERS ADD PASSWORD_DIGEST PASSWORD_DIGEST; sql> UPDATE USERS SET PASSWORD_DIGEST = 'DES-CRYPT'; sql> COMMIT;
NOTE: If it is a completely new installation of InterBase you do not need to run the SQL commands.
The ALTER DATABASE command can only be run by the database owner or SYSDBA. This command modifies RDB$DATABASE.RDB$PASSWORD_DIGEST to the string value "SHA-1". This means that all new password hash generation for new or existing user accounts in the USERS table will use the SHA-1 hash function.
The password hash function can be reset to DES-CRYPT using the same DDL:
ALTER DATABASE SET PASSWORD DIGEST 'DES-CRYPT';
The admin database is now prepped so that new user accounts or modifying the password of existing accounts will generate SHA-1 password hashes against plaintext passwords up to an untruncated length of 32 significant bytes.
GSEC [add | modify], IBConsole, and the IB Services API support the SHA-1 password hash algorithm. Any of these tools can be used to maintain the passwords of server-wide user accounts. If an existing user account has had its password changed then that user must log in to the server using the new IB client library.
Caution: There will be backward compatibility problems if the converted admin.ib database is backed up and restored by an older IB engine after the password hashes have been converted to SHA-1. Older IB engines will not understand the different password hashes and will cause unrecoverable login errors.
There is now a larger database cache setting for 64-bit InterBase. The limit for the 64-bit engine is 75 million pages, as compared to 750K pages for 32-bit engines.
InterBase XE now provides support for the EXECUTE STATEMENT functionality.
This feature enhances the InterBase Stored Procedure language. Once this is implemented, Stored Procedure developers can embed three variations of EXECUTE STATEMENT within their Stored Procedures. The variations depend on the number of rows returned from the EXECUTE STATEMENT command. The three cases are: No rows or data returned; One row of data returned; and Variable number of rows returned.
No Rows or Data Returned
EXECUTE STATEMENT <statement> <statement> ::= a SQL statement returning no rows of dataExample:
CREATE PROCEDURE EXEC_STMT_NO_RET (proc_name varchar(20)) AS DECLARE VARIABLE EMPNO INT; DECLARE VARIABLE EXECSTMT; BEGIN SELECT MAX(EMP_NO) from EMPLOYEE into EMPNO; EXECSTMT = 'EXECUTE PROCEDURE' || proc_name || '( ' || cast (EMPNO as varchar(10)) || ')'; EXECUTE STATEMENT EXECSTMT; END
One row of data returned
EXECUTE STATEMENT <select-statement> INTO :<var>[, :<var>..] <select-statement> ::= SQL statement returning one or no rows of data <var> ::= valid procedure variable, the ":" is optional.Example:
CREATE PROCEDURE EXEC_STMT_SINGLETON (TABLE_NAME VARCHAR(50)) AS DECLARE VARIABLE MAXEMPNO BEGIN EXECUTE STATEMENT 'SELECT MAX(EMP_NO) FROM' || TABLE_NAME INTO :MAXEMPNO; SUSPEND END
Any number of data rows returned
FOR EXECUTE STATEMENT <select-statement> INTO :<var> [, :<var> ..] DO <compound-statement> <select-statement> ::= SQL statement returning one or no rows of data <var> ::= valid procedure variable, the ":" is optional.
CREATE PROCEDURE EXEC_STMT_ANY (TABLE_NAME VARCHAR(50), INT_FIELD INTEGER)
RETURNS
(INT_RETVAR INTEGER)
AS
DECLARE VARIABLE IFIELD INTEGER
BEGIN
FOR EXECUTE STATEMENT
'SELECT' || INT_FIELD || 'FROM' || TABLE_NAME INTO :IFIELD
DO
IF (IFIELD = 0) THEN
INT_RETVAR=0;
ELSE
INT_RETVAR = INT_RETVAR+IFIELD;
SUSPEND;
END
The following table displays the new error messages added:
| SQL Code | Error Number | Error Message |
| -204 | 335544850 | EXECUTE STATEMENT could not prepare statement : <string> |
| -204 | 335544851 | SQL statement invalid as it returns no records. SQL : <string> |
| -204 | 335544852 | Parameter mis-match for the statement : <string> |
| -204 | 335544853 | Could not execute statement : <string> |
| -204 | 335544854 | EXECUTE STATEMENT fetch error |
| -204 | 335544855 | EXECUTE STATEMENT in this form must return single row, not multiple rows. |
| -204 | 335544857 | Sql statement not allowed in EXECUTE STATEMENT : <string> |
Please note the following when using EXECUTE STATEMENT:
This feature is only available in InterBase XE and is not backward compatible.
Sweeping a database is a systematic way of removing outdated records. Periodic sweeping prevents a database from growing too large. In the past sweeping slowed system performance and users disabled the automatic database sweep function because of the impact on product operations.
InterBase databases periodically need to be swept. Otherwise the main memory allocated for each transaction's bitmap increases to the point where performance becomes unacceptable. The longer sweep takes to complete, the more main memory requirements increase for starting new transactions.
With the implementation of the fast sweep optimization in InterBase XE, the memory allocation issue has been mitigated. The user has the option to configure their databases for automatic sweep. In cases where large databases have large archival or infrequently modified tables, a database sweep will have minimal impact on the performance of running transactional operations.
There is no new user interface or action required by the user to enable this functionality. Manual sweep initiated by the GFIX command line tool, IBConsole, or programmatically, as well as automatic sweep configuration on a database, use the fast sweep mechanism.
A database needs to be created or backed up and then restored to ODS15.
The term blocking factor is used to denote the number of records stored in a block. InterBase employs a single database-wide blocking factor that maximizes the number of rows that can be stored on a data page.
In InterBase XE, ODS 15 databases introduce table-specific blocking factors that optimize how many rows can be stored on a data page and minimizes the row number assigned to a row. In addition, the engine minimizes the size of a number of run-time data structures. This is especially important as tables storing a very large number of rows and accessed by a large number of database connections can cause excessive memory consumption.
Databases with tables containing a large number of rows or is expected to grow to a large number of rows benefit from table-specific blocking factors. It allows those tables to store more rows in the same record number space, while using less memory for run-time retrieval data structures.
There is no user interface or any action required by the user to enable this functionality. The table-specific blocking factors are set automatically after a database restore.
The blocking factor values for individual tables can be observed in the system columns:
If a table does not have a table- specific blocking factor, this system column will query as NULL. Each time a database restore is performed, these blocking factors are retuned for the actual row data restored. Therefore, it is possible that these values will change over time as the database is modified and is backed up and restored.
If an ODS 15 database has been created and loaded with data, taking a backup and restoring will set the table-specific blocking factors.
With the ODS 15 databases the maximum index key size limit is increased. Now larger column data can use this for both single-byte character sets and multi-byte (such as UTF8) columns.
Because InterBase XE supports UTF8 and multiple other multi-byte character sets, the limit has been increased. For example, a single-column key using 4-byte UTF8 character would calculate to 1020/4 = 254 UTF8 characters with a 4KB page size.
ODS 15 databases automatically allow index definitions where the underlying key size is now a factor of the database page size.
Databases created with engines enabled with this functionality cannot be moved back to older versions of InterBase.
Also a database restore to a smaller page size will fail if indexes with a large key size cannot fit within limit specified above.
No user interface or actions are required by the user to enable this functionality. Each time a database restore is performed, the indices are recreated.
Only ODS 15 and later databases have support for larger index keys. If you want to use this facility, restore your database to ODS 15. Other indices that use a smaller size than 252 bytes continue to have the same on-disk storage without any penalty.
When restoring a database with InterBase XE, get the error unassigned code. With databases with a long lineage or databases backed up with InterBase 2009 and restored with InterBase XE, each case has different metadata security settings. So when selecting a system table (for example: RDB$RELATIONS) you get the error message: no permission for read/select access to table RDB$RELATIONS by user SYSDBA.
This error occurs with databases which have these criteria:
This behavior is exhibited due to stricter enforcement of meta data rights in InterBase XE during the restore of a database.
Solution:
To resolve this problem execute readmeta.sql against your database before you back it up. readmeta.sql may be found in
Explanation:
The problem occurs with databases that have a long lineage. The two cases are (1) a database has a restore history of IB6->IB7->IB2007->IB2009->IBXE; and (2) a database backed up and restored as IB2009->IBXE. Each case has different metadata security settings. The first instance never had metadata security because it originated from IB6. However with the second instance, it was created (not restored) by IB2009 with a full complement of security privileges for all system tables.
With the first case, the database was backed up and restored and with each succeeding release, the new release would install privileges for the new system tables in that release (think RDB$USERS, RDB$ENCRYPTIONS, RDB$ROLES, etc.). But it couldn't alter the original system tables because it had no way of knowing if the database owner had already altered their security privileges. For example, a user might have revoked all privileges to RDB$TRIGGERS and RDB$PROCEDURES to conceal their trigger and stored procedure code.
Also, in the first case, a SYSDBA may have run readmeta.sql years ago and refined the metadata from that baseline to a custom security profile. InterBase cannot override that customization by automatically resetting it after the XE restore. InterBase XE can't assume that every database it restores should unconditionally install the default metadata privileges because it doesn't know the history of individual databases.
So it is recommended to run readmeta.sql, which sets the default or starting point for configuring it the way you want it. This advice is independent of whether you are migrating to XE.
Example using isql:
isql "path to database" -user sysdba -password masterkey -i readmeta.sql
Executing readmeta.sql with IBConsole
Databases originally created before InterBase 6.5 may have the error: no permission for read/select access to table RDB$XXXX by user SYSDBA with InterBase XE.
Solution:
InterBase XE enforces tighter meta data security and this error may result from doing meta data operations on databases originally created with versions of InterBase prior to version 6.5. Meta data operations involve requesting information about system objects such as listing system objects or updating them and using the Performance Monitor.
To resolve this error you need to perform two similar operations. The first operation grants rights to system tables. To do so, execute readmeta.sql from the examples\security folder in your InterBase install directory.You can execute readmeta.sql against your database using isql or IBConsole.
Example using isql:
isql "path to database" -user sysdba -password masterkey -i readmeta.sql
Executing readmeta.sql with IBConsole
Second, you need to grant rights to system temorary tables if you are going to do performance monitoring. Due to potential security concerns, most installations will want to grant rights for system temporary tables only to sysdba and the database owner, which is what is presented below. If you wish for all users to be able to view system temporary tables, modify this example to GRANT TO PUBLIC. Some installations will want only specific users to have rights, in which case a more customized script may be needed.
To grant rights for system temporary tables, save the following as a text file, then execute it the same as readmeta.sql above.
create procedure granttmp as
declare variable stmt varchar(1024);
declare variable ownername varchar(66);
declare variable tablename varchar(66);
begin
select rdb$owner_name from rdb$relations where rdb$relation_name = 'RDB$RELATIONS'
into :ownername;
for select rdb$relation_name from rdb$relations where rdb$system_flag>0 and rdb$relation_name starts with 'TMP$' into :tablename do
begin
stmt = 'grant all on ' || tablename || ' to sysdba';
execute statement stmt;
stmt = 'grant all on ' || tablename || ' to ' || ownername;
execute statement stmt;
end
end;
execute procedure granttmp;
drop procedure granttemp;
commit;
exit;
The 16-bit UNICODE character sets UNICODE_LE and UNICODE_BE only work for Server character sets. These character sets cannot be used as a client character set. If your client needs full UNICODE character support, please use UTF8 instead of UNICODE_LE and UNICODE_BE for the client character set (aka LC_CSET). A client can use the UTF8 (or other native) client character set to connect with a UNICODE database.
InterBase XE supports no defined UNICODE collations in this release. The default collation is binary sort order for UNICODE.
Windows Error Reporting (WER) dialog pops up intermittently if and when an InterBase server crashes.
Resolution: We are working on fixing any crashes that we are aware of. In the meantime you can disable the Windows Error Reporting dialog from popping up by modifying the Windows Registry thus. Set the registry attribute HKEY_CURRENT_USERS\Software\Microsoft\Windows\Windows Error Reporting\DontShowUI value to 1 to disable. This is as per recommendation of MSDN article http://msdn.microsoft.com/en-us/library/bb513638(VS.85).aspx. We may address this configurable option from within ibserver.exe in future builds by informing WER to disable this only for InterBase server binary.
The following are resolved defects for InterBase XE.
| Internal Defect # | External Defect # (QC) | Description |
| InterBase XE Update 3: August-2011, Bugs Fixed in 10.0.3 Version | ||
| INTB-1228 | Insert statement causes Server crash. | |
| INTB-1215 |
This issue lists all IBConsole-related fixes in this update. 97534 When providing the password for a column encryption in Interactive SQL, an Access violation error message shows up. 97480 When altering a column to decrypt it, an error message shows up, but the column is decrypted. 96412 When starting the server from IBConsole, you receive an error message saying that the server can't start, even though the server is actually running; when connecting to a database, you receive an AV error message. 89388 When using the "New Connection" option from the Tools menu in the IBConsole, an AV error message shows up. 67161 UTF8 is missing in combo box for default character set. 97683 The memo dialog box that opens when you see the value for the RDB$DESCRIPTION field should not be read-only. |
|
| INTB-1210 | Enhancement request to strengthen backup and restore operations on databases with DES encryption keys (allow only as a service). | |
| INTB-1208 | ISQL Extract (-x/-a) operation does not respect user authentication parameters. | |
| INTB-1204 | InterBase server on Linux stops accepting connections after hours of extensive use. | |
| INTB-1178 | Blob error on backup after restoring a database with -i. | |
| INTB-1170 | Installing InterBase to a very long directory path causes a server crash on local Windows database connections. | |
| INTB-1162 | Adding a member to a role doesn't work in IBConsole. | |
| INTB-1149 | Silent installer allows installation to c:\Program Files. | |
| INTB-1148 | 64 bit installer fails to write the InterBase root directory to registry when the directory name contains a space character. | |
| INTB-1141 | InterClient does not expose certain IB Error Codes like isc_deadlock. | |
| INTB-1133 | Database aliases do not work for local connections on Windows. | |
| INTB-1130 | 94120 | interbase.msg not found in Client Only install. |
| INTB-1124 | 94455 | SQL Unicode Char Type failure. |
| INTB-1116 | Env. variables case: Operations Guide PDF, Chapter 4 "Server Configuration", sub-section "Using environment variables". | |
| INTB-1115 | IBConsole database encryption wizards not working. | |
| INTB-1105 | GFIX doesn't work with 2 switches at the same time, if the second switch is Write or Validate. | |
| INTB-1099 | GFIX doesn't change the write mode for a database when setting Buffers and Write Mode at the same time. | |
| INTB-1092 | 93524 |
GBAK fails if database file path contains spaces AND using InterBase Services. If you are providing file path names with embedded spaces in them and using the InterBase service manager (-service switch in GBAK), you will need to multi-quote the file names:
The above is required because the command shell strips away the external double_quotes and only leaves the internal single_quotes for InterBase to know that it is a single string value.
For example: |
| INTB-1090 | Database entities (procedures, tables, encryptions) with space in the name (delimited identifier) gets truncated when setting/checking access privilege. | |
| INTB-1080 | ToGo Edition crash at end of backup or restore service execution from Delphi application using IBX components. | |
| INTB-1066 | Delphi XE build application using dbExpress causes InterBase server crash during text blob retrieval. | |
| INTB-1007 | DataDirect ODBC driver ignores Dialect 3. | |
| InterBase XE Update 2: March-2011, Bugs Fixed in 10.0.2 Version | ||
| INTB-1054 | XE client compatibility issue (with encryption and service manager). | |
| INTB-1052 | 90926 | ISQL crashes when "Show Procedures" command is issues if the database contains a stored procedure using UDFs. |
| INTB-1051 | 92451 | Server crashes when executing statement with grouping by text blob field, when blob data length is greater than 126 bytes. |
| INTB-1035 | Unable to restore AppWave database backup. | |
| INTB-1033 | Count of a query involving a join and a left join returns zero | |
| INTB-1031 | Inconsistent EVENT behavior. | |
| INTB-1015 | Server vulnerability with malformed packets. | |
| INTB-1008 | A parameterized query based on a union fails to return rows second time it is executed. | |
| INTB-1004 | InterBase XE Japanese InstallAnywhere installer creates invalid registry entry. | |
| INTB-1000 | 90879 | InterBase server crashes during validation phase, after database restore. |
| INTB-998 | 90582 | OUTER JOIN query returns wrong result in InterBase XE (and works well in InterBase 2009). |
| INTB-985 | Cannot establish a secondary connection for event processing for server behind a NAT router. | |
| INTB-954 | 89559 | Some queries with lots of ANDs and ORs cause server crash. |
| INTB-912 | TCS: EX_NUM_ARRY_01 crashes ibserver on MacOS 10.6. | |
| InterBase XE Update 1: December-2010, Bugs Fixed in 10.0.1 Version | ||
| INTB-890 | Sysdba has no metadata rights to databases created with InterBase 6.0 or earlier which have not had readmeta.sql applied. Raid 280556 was this same problem. | |
| INTB-860 | InterBase crashes with a specific database when a foreign key is added. | |
| INTB-853 | SELECT count() returns BIGINT - compatibility issue with existing driver/applications. | |
| INTB-839 | 88501 | Sweep while inserts are happening on a database with journaling causes the server to hang and a corrupted database. |
| INTB-824 | Investigate InterBase XE 64-bit server crash when querying for statistics using InterBase service manager. | |
| INTB-822 | RAID 280541: Server crash on ODS 13.1 database with complicated metadata script. | |
| INTB-818 | 88241 | Internal gds software consistency check (can't find shared latch (300)) error with multiple connections. |
| InterBase XE: November-2010, Bugs Fixed in 10.0.0.304 Version (UNIX builds) | ||
| INTB-791 | When JAVA application connect/disconnect/operate to OTW port, IBSever claims "SSL_READ: SSL_ERROR_ZERO_RETURN" most of the times. This is a harmless issue, and does not cause any functionality issues. | |
| INTB-756 | IBConsole: crashes when pressing the F5 key. | |
| INTB-661 | 62444 | RAID 260610: Examples are built on UNIX but do not run successfully. |
| INTB-673 | 57839 | RAID 279453: LEFT JOIN operation returns wrong result. |
| INTB-546 | 74055 | Parameter's incorrect descriptor lengths showing up inside UDFs. |
| InterBase XE: September-2010, Windows | ||
| INTB-772 | 37729 | RAID 279996: An error occurs when trying to create or change a password that begins with a question mark. |
| INTB-675 | NullPointerException (instead of an sql error message) thrown when losing the network connection and trying to run a query. | |
| INTB-671 | 79851 | RAID 273825: getMetaData(). getPrecision() returning wrong value. |
| INTB-670 | 48152 | RAID 251980: JOIN of 2 stored procedures give "arithmetic exception" error. |
| INTB-669 | 81786 | RAID 278498: Increase request impure space size from the current 256K limit to a larger value. |
| INTB-659 | 62255 | RAID 260612: QLI crashes as soon as "SHOW FUNCTIONS" command is given. |
| INTB-654 | 50375 | RAID 260671: OnlineDump with multiple files. |
| INTB-653 | 55499 | RAID 260629: Inserting from VARCHAR field in one table to BLOB in another table inserts additional junk in the target table. |
| INTB-650 | no T privilege with grant option on table/view TableName. | |
| INTB-597 | 2311 77931 |
RAID 146832: ORDER BY using an index on a DATE column gives wrong order. |
| INTB-547 | 365 | RAID 279571: Non-SYSDBA db owner SELECT fails even with GRANTED rights on the table. |
| INTB-538 | RAID 273806: Optimizer regression in JOINS since InterBase 2007 Service Pack changes. | |
| INTB-523 | 77315 | COALESCE and aggregate functions. |
| INTB-513 | RAID 191536: The java.sql.DatabaseMetaData.getColumns() method returns incorrect data type for arrays and blobs. | |
| INTB-493 | IndexOutOfBoundsException thrown when calling PreparedStatement executeBatch(). | |
| INTB-402 | Unexpected behavior of database linger. | |
| INTB-355 | Parameterized query params order in SQLDA/SQLVAR not the same as visual order of question marks. | |
| INTB-319 | Possible Optimizer regression with fixes in the InterBase 2007 SP3. | |
| INTB-267 | Create Database from JDBC application does not respect character set requested. | |
| INTB-264 | RAID 272543: RDB$FILTERS does not have a unique index on filter name leading to duplicate filters. | |
| INTB-253 | RAID 270024: InterBase cannot use 2GB+ database cache even if Large Address Aware flag was set. | |
| INTB-236 | RAID 271600: "Request Synchronization error" reported on 8-core system with heavy activity. | |
| INTB-235 | RAID 270959: Accessing ODS 10.x database leads to server crash. | |
| INTB-151 | RAID 269627: Unique superkey license files belonging to the same "addon" package are all not loaded by the licensing engine. | |
| 3424 | When you open the Properties form for a table or procedure and select the Permissions tab, the column headers rarely appear. If you select another tab and then come back to the Permissions tab, the column headers will be there. | |
| 4989 | I add a UDF with a param of type DATE, the UDF is created, but when I try to show the property of the UDF, IBConsole shows the Message: 'unsupported Datatype' The UDF cannot be dropped in IBConsole. The UDF works fine in ISQL, and can be dropped in ISQL This happend also with TIMESTAMP and TIME. | |
| 6714 | Create a table in an InterBase database and fill it with data. Then export the table to a Comma Seperated Value file using IBConsole and the export works fine. Check the exported file using MS Excel and it appears to be fine. Then empty the table. But when I try and import data from the .csv file that I exported the table to, I get the following message: Access Violation at address xxxxxxxx in module 'IBConsole.exe' Read of address 000000000. This is the case with any .CSV file that I try to import data from. | |
| 63968 | Database Restore Fails: "No current record for fetch operation". | |
| 68637 | DB Restore can't be done on IBconsole. | |
| 74598 | The name of the directory that contains the IBConsole.xml file is misspelled. | |
| 75028 | When trying to change the data type for a domain, an error appears. | |
| 76342 | Metadata names longer than 22 characters are truncated. | |
| 76616 | When trying to connect as a different user from the InteractiveSQL, the connection window opens but it doesn't connect as a different user and an error message appears. | |
| 76622 | When disconnecting from a database using the InteractiveSQL then trying to reconnect to the database, an error message appears. | |
| 79418 | When using the IBConsole for creating a journal, a journal archive, and to archive the database, the Archive Database option returns an error message (this fails for all types of connections. | |
| 79420 | When creating a journal, a journal archive and a database archive for a database, using Interactive SQL, the 'Archive Database' option doesn't refresh after disconnecting from the database and then reconnecting to the database. | |
| 80580 | IBConsole Open Table, Error. | |
| 81324 | Interactive SQL in IBConsole: truncated RDB$ names. | |
| 82503 | When creating a database then a generator using Interactive SQL, an error appears. You then have to use Task Manager to terminate the process. | |
| 82706 | When using a field that can be null in the Primary Key constraint definition, then removing it from there, an error appears. | |
| 82776 | When creating an external function with an entry point larger than 67 chars, an unclear error message appears. | |
| 82829 | When altering a view to add a second column, the table name is added incorrectly. | |
| 82859 | When altering a trigger by adding a local variable with the same name as another variable, then changing it back to the way it was, the changes cannot be made. | |
| 82904 | When choosing a value larger than 10 digits for the input type of a blob filter, an error message appears and the Blob Filter Editor window closes. | |
| 83369 | When choosing the 'New Connection' option from the Tools menu to connect to a different database then what is running a query, the IBConsole shuts down. | |
| 83370 | When trying to see the License Manager from the Tools menu of the IBConsole, an error message appears. | |
| 83820 | When trying to create a blob filter with a duplicate name, the Cancel button doesnt work. | |
| 83881 | When creating a database with a name that already exists, the Cancel button doesn't work. | |
| 84783 | Text cannot be copied inside the name area of procedures and triggers, even if the focus is inside the name area; the text is added inside the body area. | |
| 84934 | When using the IBConsole to encrypt a database, then deleting the encryption from the system table of encryptions and changing the value of EUA, an AV error message appears. | |
| 85054 | When performing a database sweep using the IBConsole, the text of the confirmation message isn't correctly aligned. | |
| 85104 | For InterBase XE, License Manager from the Tools menu of the IBConsole doesn't open, and an AV error message is shown instead. | |
| 85514 | When using the IBConsole to run a couple of queries without committing, disconnecting the database creates an AV error message. | |
| 86294 | When connecting to a database as sysdso using IBConsole and trying to view data from a table that the user has select permission on, an error message appears. | |
| 86737 | EUA_USER and EUA_PASSWORD options must be added to Database Restore. | |
| 86739 | IBConsole should be using the new camel-cased and case-sensitive OTW parameter names (for IB OpenSSL clients). | |
| 86749 | SELECT COUNT(*) and SELECT AVG should return a SQL_INT64 type. If there is any code in IBConsole that uses 32-bit integer type local variable to receive this value, it should be changed to a 64-bit integer type. | |
| 86924 | IBConsole requires full path to backup file. | |
| Documentation Updates: Sept-2010, Windows | ||
| INTB-773 | Language Reference Guide: Chapter 3: WHEN...DO. Updated GDSCODE errcode. Also updated Table 5.5 with correct GDSCODE usage. | |
| INTB-769 | Operation Guide: Appendix B: Table B.1 InterBase Specifications. Updated maximum size of external table file. | |
| INTB-744 | Developers Guide: Chapter 14: Applying Cached Updates with a Dataset Component Method. Replaced old procedure example with a new IBTransaction1 example. | |
| INTB-739 | Language Reference Guide: Chapter 6: Table 6.34. Added table RDB$USERS. | |
| INTB-736 | Embedded SQL Guide: Chapter 13: Topic: SQL Datatype Macro Constants. Updated information on sqlsubtype settings. | |
| INTB-735 | Developers Guide: Chapter 6: Table 6.7. Updated integer information. | |
| INTB-734 | API Guide: Chapter 3: Environmental Variables Used by Interbase. Added two new variables: IB_PROTOCOL and INTERBASE. | |
| INTB-733 | Language Reference Guide: Chapter 6: Topic: RDB$DATABASE. Added missing fields to table 6.1. | |
| INTB-731 | Language Reference Guide: Chapter 2: ALTER TABLE, ALTER DATABASE, CREATE ENCRYPTION, CREATE TABLE. Added note to each topic: For detailed information on encryption and decryption, see the topics Encrypting Data(page 13-9) and Decrypting Data (page 13-11) in the Data Definition Guide. | |
| INTB-728 | 22384 | Operation Guide: Chapter 4: Topic Using ibmgr to Start and Stop the Server. Instructions for starting InterBase under the interbase user account have been updated. |
| INTB-726 | API Guide: Chapter 5: Added new topic: Use of Commit/Rollback with Multidatabase Transaction. | |
| INTB-725 | Developers Guide: Chapter 6: Explanation of dsc_flags. Added DSC-systems information to Table 6.5. | |
| INTB-723 | Updated installation information. Desktop and ToGo setups are only available for Windows O.S. | |
| INTB-722 | Embedded SQL Guide: Chapter 6: Topic Using Comparison Operators in Expressions. Added Table 6.4 listing comparison operators in expressions. | |
| INTB-720 | 5253 | RAID Issue 171696: Developers Guide: Accessing InterClient extensions to the JDBC. Added a suitable example for how to cast the JDBC driver object. |
| INTB-719 | RAID Issue 259389: isc_dpb_archive_journals and isc_dpb_archive_database not listed in documentation. | |
| INTB-718 | RAID Issue: 217986: Operation Guide: Appendix A: Topic: New InterBase Keywords. Need the new Keywords introduced in InterBase 7.5 and above. | |
| INTB-515 | The Operations Guide PDF (page 5-10 to 5-12) details the various OTW parameters that can be used by InterBase native and JDBC applications. With InterBase XE, the older named parameters can be removed from the table and ONLY the new ones mentioned. Note, the new OTW parameters are case-sensitive and hence the documentation in the above pages need to be cleaned up with exact camel-casing of OTW parameters. | |
| INTB-43 | Small omission in Language Reference Guide. Field rdb$depended_on_type and rdb$dependent_type do not list types 11 and 14. 14 is External Functions. 11 is a generator. | |
| RAID Issue 112111: Operation Guide: Chapter 11: Topic Edit. On Windows platforms, EDIT calls the text editor specified by the EDITOR environment variable. If this environment variable is not defined, then EDIT uses the Microsoft
|
||
| RAID Issue 251988: Operation Guide: Chapter 9: Journaling Tips and Best Practices. Updated CHECKPOINT LENGTH information. | ||
| RAID Issue 218084: Language Reference Guide: Chapter 6: TMP$STATE field not documented in description for TMP$DATABASE. | ||
| RAID Issue 263959: Data Definition Guide: Chapter 13: gbak examples on page 13-17 have invalid syntax. | ||
| 23253 | RAID Issue 238178: Language Reference Guide. Chapter 2. The SQL example for the CASE statement won't work because it is truncated. | |
| RAID Issue 194123: Language Reference Guide. Chapter 2. Yearday for extract is listed as returning values 1-366. It should say 0-365. Hour and minute are similarly wrong. They are listed as going from 1-23 and 1-59. They should list 0-23 and 0-59. | ||
| RAID Issue 256520. API Guide. Chapter 15. Signature for "isc_dsql_batch_execute()" incorrectly includes "isc_db_handle *db_handle". Signature for "isc_dsql_batch_execute()" incorrectly includes declaration using "ULONT Signature for "isc_dsql_batch_execute()" incorrectly includes declaration "int dialect" when actually the argument is implemented as an "unsigned short" in ibase.h |
||
| RAID Issue 240455. API Guide. Chapter 15. isc_string_too_large error is generated when SQL is greater than 64K. 64K should be changed to 2 GB. | ||
| RAID Issue 218053. Language Reference Guide. Chapter 2. ALTER DATABASE describes it as "Adds secondary files to the current database." This does not consider other new actions that can now be taken. Changed to "Changes the characteristics of a database". | ||
| RAID Issue 120748. API Guide. Chapter 3. Remove ISC_DATABASE from Table 3.1. It is not implemented any longer. | ||
| RAID Issue 106998. Operations Guide. Chapter 7. Error OBJECT database_name IS IN USE is incorrect. | ||
| 5742 | RAID Issue 192587. Data Definition Guide. Chapter 8. Documentation says you cant use UNION when creating a VIEW in DSQL. This hasnt been true since IB 5.6. | |
| 84435 | RAID Issue 276427. Data Definition Guide. Chapter 14. UTF_8 Maximum character size is changed from 1 byte to VARCHAR(63). | |
| InterBase 2009 Update 4: | ||
| INTB-412 | RAID 275463: Running delete statement two times causes constraint error, which causes the server to crash. | |
| INTB-411 | RAID 275462: Database corruption reported when deleting records from table with missing foreign key constraint index. | |
| INTB-384 | Indexes entries lost on savepoint rollback for updates across nested savepoints. | |
| INTB-356 | RAID 274857 and 274858: Table's current format descriptor can be garbage collected during sweep. | |
| INTB-331 | RAID 273917: gds32.dll not getting installed in system 32 directory. | |
| INTB-305 | During certification, ibserver often starts claiming errors into the interbase.log recursively until it has taken up the whole disk space. | |
| INTB-292 | Prepared statement query fails on UTF8 database. | |
| INTB-281 | InterBase server crashing with a batchupdate query from Java. | |
| INTB-252 | RAID: 272016: Event listener does not work with native OTW connection string in InterBase 2009 Update 2. | |
| INTB-249 | Trying to connect to OTW port without OTW settings causes client hangup. | |
| INTB-231 | RAID 270898: When executing SQL statements, JDBC driver returns SQL Warning beside the normal result, even on success. | |
| INTB-230 | Client crashes on DSQL error when interbase.msg cannot be found. | |
| INTB-228 | Wrong table name: Language Reference Guide: Table 5.3 refers to Table B-4. Should refer to Table 5.4. | |
| InterBase 2009 Update 3: | ||
| RAID 263854: Hot links from within the PDF documents to other PDF documents come up with an error. | ||
| RAID 268798: Inner join with Stored Procedure that selects from the same table results in "No current record for fetch operation." | ||
| RAID 270024: InterBase cannot use 2GB+ database cache even if Large Address Aware flag was set. Check Operations Guide PDF manual, chapter: InterBase Limits section Various InterBase Limits, Table B1, for new updates. Search for maximum number of cache pages per database description. | ||
| RAID 270898: When executing SQL statements, JDBC driver returns SQL Warning beside the normal result, even on success. | ||
| RAID 270959: Accessing ODS 10.x database leads to server crash. | ||
| 271600 | 75561 | "Request Synchronization error" reported on 8-core system with heavy activity. |
| INTB-146 | RAID 268798: Inner Join with Stored Procedure that selects from the same table results in "No current record for fetch operation". | |
| INTB-147 | RAID 270284: Complicated query involving joins between tables and stored procedures runs very slowly. | |
| INTB-150 | RAID 270017: Multiple clients concurrently executing ALTER TABLE statement against different databases results in client error or hang. | |
| INTB-152 | RAID 269558: Online Dumps are missing 1 record after multi-client activity. The record is present in the source database, but is not included in the online dump. | |
| INTB-153 | RAID 269555: Online Dump files have corrupted indexes and page errors when taken from an encrypted database during multi-client activity. | |
| INTB-155 | RAID 269200: IBConsole Help is out of date on Windows Vista. | |
| INTB-156 | RAID 268686: InterBase client on Windows Terminal Services reports "Cannot attach to Services Manager" when run for extended period of time, or if the server is subject to intense database activity. | |
| INTB-157 | RAID 267667: Page xxxx wrong type (expected 7 and encountered 5) after many hours of stressful INSERT activity from numerous simultaneous clients. | |
| INTB-159 | OTW/SSL connections do not work via InterBase JDBC driver. Check Developer's Guide PDF manual, chapter "Programming with JDBC" section "SSL file properties" for new updates. | |
| INTB-168 | RAID 270396: Java clients are unable to connect to databases that require a System Encryption Password (SEP). | |
| INTB-229 | Missing Error Message. | |
| INTB-230 | Client crash on DSQL error when interbase.msg cannot be found. | |
| InterBase 2009 Update 2: | ||
| RAID 254988: Query with explicit and implicit joins results in "no current record for fetch operation" error. | ||
| RAID 256996: Distinct in nested queries can return incorrect results. | ||
| 65388 | RAID 257272: Concurrent delete and select (and probably insert) cause database to be corrupted. 'internal gds software consistency check (exceeded index level)" error in interbase.log. | |
| 57839 | RAID 257670: Join with Stored Procedure returns incorrect results. | |
| RAID 259585: Inner Join between two views which both have left joins results in error "no current record for fetch operation." | ||
| RAID 260489: If journal files are lost, connecting to the database may fail. Fix notes: A new GFIX switch (-disable wal) is provided to disassociate a database from its journal files. No cleanup of the journal files or journal archive files is attempted and it is the case that committed data may have been lost. This could occur because the lost or inaccessible journals may have committed data that was never applied to the database files proper. However, it becomes possible to attach the database to access existing data contained therein. |
||
| RAID 261953: Rogue TCP packet could cause server crash. | ||
| RAID 261974: Server crash with big SORTMEM_BUFFER_SIZE on restore. | ||
| RAID 263533: OTW: malformed connection string leads to server hang. | ||
| RAID 265145: Invalid data entered into a Unicode column hangs client on retrieval operation. | ||
| RAID 265481/2: Journaling and encryption combination fails with "decryption of encryption value failed?" | ||
| RAID 265601: Running GBAK as a service incurs high CPU usage in the server. | ||
| RAID 265824: Queries based on fields where the character_set_name and collation_name do not match and there is an index return no records. | ||
| RAID 265905: Security vulnerabilities exploited by rogue clients. | ||
| RAID 267372: InterBase cannot propagate events on both interfaces of a multihomed host. | ||
| RAID 267433: Exceptions only display first 67 characters. They should display 78 characters. | ||
| RAID 267550: Server crashes with BUS alignment error on Solaris 10. | ||
| 70915 | RAID 267860: Sweep under some conditions causes error "Maximum user count exceeded" and "Request depth exceeded for IRQ_93" in interbase.log. | |
| RAID 267874: Many users doing many inserts causes InterBase server crash with seg fault on Windows or Solaris if there are multiple CPUs. | ||
| RAID 267963: After connecting to employee.gdb, subsequent validation of the database with gfix results in interbase.log having numerous "Page xxx is in use but marked free". | ||
| RAID 268016: InterBase Services API has problems working on Windows Terminal Serivce. | ||
| InterBase 2009 Update 1: | ||
| 65969 | Backup/Restore of encrypted databases not supported in IBConsole. | |
| RAID 265043: Encryption failed when database or column has a character set. | ||
| RAID 265241: Re-encrypting a column crashes the server. | ||
| RAID 258311: Restore using gbak with buffers set high and -o (one at a time) causes server to crash. | ||
| JDBC: DataBaseMetadata.getTables() does not work with delimited tables/columns. | ||
| JDBC: DataBaseMetadata.getTables() wrong ordering of result set. | ||
| JDBC: does not recognize InterBase 2009 reserved words. | ||
| InterBase 2009: | ||
| RAID 240075: Running gfix -validate -full exhibits index corruption messages on table RDB$DEPENDENCIES. | ||
| RAID 252301: IBMgr Cannot Start Server As A Service When Launched Directly From The Bin Directory. Instead, must be launched from the installed shortcut which passes "InterBase Server Manager [instance = gds_db]" | ||
| 56532 | RAID 255784: Running a select statement with specific OR conditions causes the InterBase server to crash. | |
| RAID 255847: Validating a freshly restored database reports many errors in index RDB$DEPENDENCIES. | ||
| 56533 | RAID 256021: JDBC driver: Calling PreparedStatement.addBatch() more than once results in error when calling PreparedStatement.executeBatch(). | |
| 53957 | RAID 256054: IBServer crash on select from table with data indexes. | |
| RAID 257272: Concurrent delete and select (and probably insert) cause database to be corrupted. "internal gds software consistency check (exceeded index level)" error in interbase.log. | ||
| 51439 | RAID 261546: isc_info_num_buffers returns incorrect information. | |
| InterBase 2007 Update 3: | ||
| RAID 240075: gfix -validate -full exhibits index corruption messages on table RDB$DEPENDENCIES. | ||
| 34587 | RAID 251616: gfix -validate -full exhibits index corruption messages on table RDB$DEPENDENCIES. | |
| 50554 | RAID 253033: Using table alias in UPDATE statement gives error. | |
| 49895 | RAID 253303: Incorrect results from left outer join query. | |
| 50461 | RAID 253967: CodeGear InterBase Multiple Vulnerabilities. | |
| RAID 254988: Query with explicit and implicit joins results in no current record for fetch operation error. | ||
| 56532 | RAID 255784: Running a select statement with specific OR conditions causes the InterBase server to crash. | |
| 65387 | RAID 255847: Validating a freshly restored database reports many errors in index RDB$DEPENDENCIES. | |
| 53957 | RAID 256054: Server crash on select from table with date indexes. | |
| RAID 256996: Distinct in nested queries can return incorrect results. | ||
| 65388 | RAID 257272: Concurrent delete and select (and probably insert) cause database to be corrupted. "internal gds software consistency check (exceeded index level)" error in interbase.log. Join with Stored Procedure returns incorrect results. | |
| 57839 | RAID 257670: Join with Stored Procedure returns incorrect results. | |
| RAID 258311: restore using gbak with buffers set high and -o (one at a time) causes server to crash. | ||
| RAID 259585: Inner Join between two views which both have left joins results in error no current record for fetch operation. | ||
| 60873 | RAID 260621: Interbase 7.5 and 2007 Numeric Type have Bug. | |
| RAID 261974: Server crash with big SORTMEM_BUFFER_SIZE on restore. | ||
| RAID 265601: Running GBAK as a service incurs high CPU usage in the server. | ||
| InterBase 2007 Update 2: | ||
| RAID 58205: Improve access method for full outer joins. | ||
| 47598 | RAID 58257: Left outer join performance without an index fixed. | |
| 51179 | RAID 58462: Index is not used in a co-related sub select of an UPDATE statement, fixed. | |
| 47916 | RAID 60128: Left outer join with table expressions not optimized when indexes should be used, fixed. | |
| 20359 | RAID 60269: Query Optimization when using "IN" or "OR" keywords fixed. | |
| 25160 | RAID 61347: Index is not used for the where clause when the query is outer join fixed. | |
| 10264 | RAID 219990: Left join on a big table completion lag fixed. | |
| 49654 | RAID 223805: The optimizer uses a sequential table scan to perform co-related sub-query, fixed. | |
| 47599 | RAID 231879: Data inserted in the last transaction not seen if the database is made read only, resolved. | |
| 11219 | RAID 239883: Installing Desktop Edition as Administrator does not make Programs listing available to other Users, fixed. | |
| RAID 243270: Connecting with 8.0 client to 7.1 server fails with unavailable database error, fixed. | ||
| 40486 | RAID 243299: InterBase 7.1 server crashes upon disconnect using 8.0 client with remove connection, fixed. | |
| 47604 | RAID 243679: InterBase Server Manager starts as an ordinary user even if you are an administrator on Windows Vista, fixed. | |
| RAID 248755: interclient.jar JDBC driver now installed as part of the InterBase SDK. | ||
| RAID 248850: Bookmarks are missing from Language Reference Manual, fixed. | ||
| 47600 | RAID 249045: InterBase 2007 Installer now works on SUSE Linux 10. | |
| RAID 249232: INSERT/COMMIT for each record delay when Journaling is enabled on some Windows platforms, fixed. | ||
| 47602 | RAID 251265: Query with many joins returns "size of optimizer block exceeded", fixed. | |
| 44565 | RAID 251608: Optimizer block exceeded error fixed. | |
| 43874 | RAID 251610: Bad query result on LEFT JOIN when multiple filters in the join, resolved. | |
| RAID 256161: Nested loops in triggers crashes the server, fixed. | ||
| InterBase 2007: | ||
| RAID 60140: Backup and Restore causes problem with adding constraints. | ||
| RAID 112113: Invalid 'CREATE SHADOW' statement will cause the ISQL crash. | ||
| RAID 120473: DEFAULT is allowed for BLOBs, but causes errors (such as Conversion error from string "BLOB") when used. | ||
| RAID 122700: FOREIGN KEY constraint DDL fails with multiple indices on REFERENCE key. | ||
| RAID 124028: IBConsole cannot see the view data. | ||
| RAID 124771: The error constraint not found is raised when one attempts to create a foreign key constraint if the parent table has both a Primary Key constraint and a separate unique index on the referenced column(s) and the name of the unique index sorts before RDB$PRIMARY. | ||
| RAID 127168: InterBase server creates databases without absolute path in System32 directory. | ||
| RAID 148143: Instead of getting the normal error message that field TI cannot be ***NULL*** you get a "conversion error from string "BLOB". | ||
| RAID 157531: Obsolete ibconfig parameters included in ibconfig file. | ||
| RAID 169965: SELECT * FROM TMP$PROCEDURES will crash server if a procedure has been dropped. | ||
| 7997 | RAID 200567: Support to INSERT and UPDATE in BLOB field with SQL command. | |
| RAID 213125: It is impossible to drop a trigger that starts with the name RDB$. | ||
| RAID 217985: List of System temporary tables (currently page 244) does not list TMP$HEAPS and TMP$TRIGGERS. | ||
| RAID 218040: Invalid INTERBASE env variable value gives misleading error. | ||
| RAID 228356: Allow connection string to a different port to specify a different port number in addition to the port label we already have. | ||
| RAID 230142: If you select 'no' for 'run interbase server as a service on Linux', it runs InterBase server as a service on Linux. | ||
| RAID 237809: Better error messages required for database re-routing failures. | ||
| RAID 238414: Select after update generates cannot update read-only view error. | ||
| RAID 238638: A connection made via a server alias will fail if other non alias connections are concurrent. | ||
| RAID 239254: Embedded data user authetication section missing from manual. | ||
| 24859 | RAID 239622: gds32.dll enhancement, require spb support for instance name. | |
| RAID 239690: Select from view which calls UDF that returns a blob can cause server crash. | ||
| 13183 | RAID 239730: Alias support for IBConsole. | |
| 28518 | RAID 239847: DataDirect ODBC driver doesn't work with SELECT procs with input params. | |
| 14563 | RAID 239880: Add support to command select, insert, update on Blob fields. | |
| 11220 | RAID 239882: Incomplete entries in Services File. | |
| 9014 | RAID 239886: Database Alias fails when database already opened via full path. | |
| 31288 | RAID 240793: BLOB as (VAR)CHAR functionality failure in Stored Procedures. | |
| RAID 241006: IBConsole crashes when you access "IBConsole help under the Help menu. | ||
If you have a valid maintenance contract with Embarcadero Technologies, the Embarcadero Technical Support team is available to assist you with any problems you have with our applications. Our maintenance contract also entitles registered users of Embarcadero Technologies products to download free software upgrades during the active contract period. Evaluators receive free technical support for the term of their evaluation. We encourage you to visit the Support section of our Web site.
Evaluators receive free technical support for the term of their evaluation. To download evaluations of Embarcadero Technologies products or to learn more about our company and our products visit us at http://www.embarcadero.com/.
Copyright 2011 Embarcadero Technologies Inc. All CodeGear brand and product names are trademarks or registered trademarks of Embarcadero Technologies in the United States and other countries. All other marks are the property of their respective owners.