What's new in FrontBase 7.2.14
May 1, 2013
- An explicit collation used for an escaped like involving any types is now selected correctly.
- Explicit per roundtrip auto commits is now handled correctly.
- Any type tiny integers was not compared as a numeric comparison.
- The SQL log file and the FrontBase log files were not controlled by the etc/FrontBase.config.
- The function "int fbcdIsCreated ( const char* url )"have been added to FBCDatabases.h. The function returns 1 if the database denoted by the url exists.
New in FrontBase 5.2.4 (May 29, 2012)
- Fix a race condition in connection with 64-bit memory access on 32-bit buses.
New in FrontBase 5.1.3f (Oct 6, 2010)
- The transaction number was exported incorrectly when exporting using the isolation level versioned.
- Collection of statistics on input output activity was not entirely correct on all platforms
New in FrontBase 5.1.3 Alpha (May 29, 2010)
- In rare circumstances was very small transactions not recorded in the transaction
- log while a backup was running.
- The execution time of LookSee queries involving or operator on large tables have
- been improved.
New in FrontBase 5.1.1 (Jan 27, 2010)
- A major upgrade which is NOT binary compatible with FrontBase 4.
- In order to migrate databases from FrontBase 4 to FrontBase 5 is is necessary to perform an export of the data to the architecture neutral format with FrontBase 4, create a new FrontBase 5 database, and import the data again.
- FrontBase 5 includes a number of new features of which the most important is the full 64 bit mode, which greatly enhance the caching capabilities of the server. Consequently it is possible to specify rdd cache larger than 1800 M.
- FrontBase 5 supports 2**60 rows per table.
- FrontBase 5 offers improved performance when dealing with many small write transactions.
- The FBExec is now started by launchd the replacement for startup items.
New in FrontBase 4.2.9 (Sep 17, 2008)
- The agent connection execution writing a backup is now throttled such that the disk is not.
- Monopolized, thus starving other agent connections.
- The query optimizers handling of in predicates have been overhauled.
- The amount of RAM used for when evaluating stored procedures have been reduced.
- Incorrect collation used in connection with a like operator on the information_schema.users table.
- Initially deferred constraints was not always checked in connection with inserts.
New in FrontBase 4.2.8 (Sep 28, 2007)
- INSERT, DELETE and UPDATE statements executed in a stored procedure called from a fired trigger were incorrectly transaction logged.
- Certain BIT(96) to CHAR(24) CASTs could crash the server.
- Incorrect optimization of a sub-select with outer column references could cause an infinite loop.
- An INSERT privilege check related to a flat-file could crash the server.
- "ORDER BY " could crash the server.
- Extremely (>255 characters) long procedure names could crash the server.
- Specifying a cache setting when creating a LookSee index would cause the server to deadlock.
- The replication mechanism failed when a blob handle was referenced more than once in a transaction.
- SELECT -(SELECT SUM(c0) FROM t0) FROM t0; caused the server to crash.
- Implementation of ON UPDATE CASCADE clause in a FOREIGN KEY constraint was incorrect in certain nested cases.
- Interval day-time literals was incorrectly transaction logged.
- Occurrence of transaction conflict in the replication management was incorrectly handled.
- The new sql92 command PROTECT [COUNT ] [DELAY ] can be used to protect as sequence of sql statements stating with the PROTECT statement and ending with and including a COMMIT or a ROLLBACK statement against transaction conflicts. If a transaction conflict is detected during the execution of the sequence of statements, the whole sequence is executed again after DELAY seconds. That process is repeated at most COUNT times. The default for DELAY is 10 and and the default for COUNT is 3.