History

February 15, 2006 - v2.6.0.2:

Enhancements:

Revamped GUI.
In case there is no primary key constraint, fields of an existing unique index will be used as unique identifier when storing PKEY/PKEY_VALUE pairs in IBLM$OPERATIONLOG.
Default value for "Max. logged key value length" in Prepare-Wizard has been increased from 20 to 24 characters. TIMESTAMP fields which are part of a primary key / unique index now fit into PKEY fields in IBLM$OPERATIONLOG without problems.
Per-default, PUBLIC gets in the Prepare-Wizard now pre-selected for granting privileges on logging tables.
Position and width of BLOB viewer window gets restored.
Logging options for a project can be stored now without the need to reconnect.
A per-project setting is available now to take trailing spaces in character fields into account when detecting field value changes.
Role icon is used for PUBLIC in the Prepare and Unprepare-Wizard.

Bugfixes:

Bug fixed: System table queries are compatible with Firebird 2.0 now.
Bug fixed: Several additional reserved key words (TIME, TIMESTAMP, TEMPORARY) as database object names are handled properly now.
Bug fixed: Detecting changes in character fields with trailing spaces has been fixed. See "enhancements"
Bug fixed: Enabling automatic record count without being connected does not throw an error anymore.
Bug fixed: "Logging generator values" will now log the transaction id properly. (Firebird >= 1.5 only).

July 19, 2004 - v2.5.0.15:

Enhancements:

INSTALLATION/COMPATIBILITY NOTES: Version 2.5 gets installed into a new directory. If you want to get rid of the old version, then you have to manually deinstall it. Once a database was prepared with v2.5 or higher, v2.1 or older isn't compatible with that database. v2.5 can be used with older prepared databases though.
Removed the annoying confirmation dialogs, used when disconnecting from the database and when closing IB LogManager.
Double click in the treeview on a table node registers/unregisters the entire table now.
Table fields in the treeview are ordered by their field position now.
Prepare Wizard: "Max. column value length" and "Max. logged key value length" values are pre-filled with the length of the longest character field (if > 255 characters) and the length of the longest character field (if > 20 characters) used in a primary key constraint.
Prepare-Wizard: Added some logic to avoid trigger name clashes due to long similar table names and the used trigger notation (trigger prefix and postfix values).
Prepare-Wizard: "Use ON DELETE CASCADE", "Create View", "Use English column names", "Integrate IBO DML-Caching Support" and "Add TRANSACTIONID column to the operation log table" are checked per default now.
Event listener facility has been added. Register events you are interested in and get notified if they are posted, for the currently connected database. This is extremely useful if you have enabled the IBO DML-Caching support during the prepare process, because an event (default name: IBO$DMLCACHE) is posted when a new record is inserted into the operation log table. That will give you an impression of the current logging activity - nearly in real-time. Check out the 'Event Listener' tab in the 'Options' dialog for some user-definable settings.
Logging options can be defined per project in the Connect to Database dialog now. The logging options in the Options dialog serve as default values when creating a new project.
New command line switches -i and -nosplash have been added. Use -i to specify the configuration file IB LogManager should use. If -i is omitted, then 'iblogmanager.cfg' is used. Use -nosplash to omit the splash screen at program start.
Column value replacement has been added (currently for the USER_NAME column only). You now can define a valid expression for the USER_NAME column, used when inserting a record into the operation log table. For example, if you have in each table a column called LASTMODIFIED which stores e.g. the user name from inside your client application, then you are able to use that column's value by defining the following column value replacement rules in the Connect to Database dialog.

User Column for DELETE: OLD.LASTMODIFIED
User Column for INSERT: NEW.LASTMODIFIED
User Column for UPDATE: NEW.LASTMODIFIED

ATTENTION: The resulting trigger must be valid for each table in the database!

HINT: This feature can only be used, if your database was prepared with IB LogManager 2.5 or higher!
External Tools facility has been added. You are able now to configure external tools which can be executed within IB LogManager. Check out View | External Tools.
Analyzing the database is much faster now.
Hungarian translation has been added. Thanks to Berényi Gábor.
Using EurekaLog for generating better error reports.
Minor performance tweaks.
Online-Help re-written with Help & Manual.

Bugfixes:

Bug fixed: "Max. column value length" in the Prepare-Wizard is now restricted to 32494 characters, otherwise preparing the database would fail due to the possible max. size of one record in InterBase/Firebird.

October 7, 2003 - v2.1.5.12:

Enhancements:

Facility to create a log database for the connected database has been added. Check out "File/Create Log Database...".
Some performance improvements, noticeable when working over a slow network connection.
Some minor tweaks.
Online-Help updated.

Bugfixes:

Bug fixed: The "Save As" dialog for "Export Logging Definition" doesn't fail now anymore when using a "/" in the project/alias name.

May 12, 2003 - v2.1.5.11:

Enhancements:

Multi-column layout in the treeview has been added, including a 'Description' column that shows the table/column description. If you provide a description for a table/column with e.g. a third-party admin/dev tool, then it is shown in that column. This makes a huge database in IBLM more readable.
Now you can specify an optional path to a log database in the Open-Dialog. This is useful if you are using the Addon IBLMPump to transfer logged data from a production database into a so called (transaction) log database. Logging definition operations will be applied on the production database, but browsing in logged data will happen in the log database. A new panel in the 'Data' tabsheet shows the path to the connected (log) database.
Buttons added for quicker access to "All Users", "All Tables", "All Operations" and "No Role" in the selection criteria area.
New toolbar button and (popup) menu item added to log current generator values. The value 'IBLM$GENERATORVALUES' is used for the table name in the operation log record. The IBLM Addon IBLMRedo is capable to interprete that operation log record to update the generator values in the destination database.
IBLM$GENERATORVALUES added to the Table drop-down box in the selection criteria area.
The ascending/descending index on the operation log table is generated on the DATETIME column now, instead of (DATETIME, USER_NAME, TABLE_NAME, OPERATION).
The ascending/descending index on IBLM$COLUMNLOGDEF isn't created anymore, but older prepared databases are still compatible with newer IBLM versions (e.g. when extracting the logging metadata definition). NOTICE: Once a database has been prepared with this or a higher IBLM version, it's recommended not to use an older (v2.1.1.6 and prior) version of IBLM!
The USER_NAME column in the operation log table has been increased to VARCHAR(31).
Default value of the context variable for transaction id logging in the Prepare-Wizard was changed from TRANSACTION_ID to CURRENT_TRANSACTION (Firebird 1.5 RC1 compliant).
"Quick Launch" Toolbar enhanced and dockable now.
New .PDF data export format available (upgraded to EMS QuickExport Package v2.8).
Online-Help updated.

Bugfixes:

Bug fixed: When resizing the BLOB Viewer window, the richtext field is resized now automatically.
Bug fixed: The partial logged warning and the BLOB not supported messages aren't dependent on the 'Show Message on succeeded operations' setting anymore.
Bug fixed: Open the 'Database Information' dialog doesn't execute activate/deactivate indices/trigger statements anymore.
Bug fixed: Dependent on the database dialect proper datatypes for primary key and foreign key columns and stored procedure parameters are used. Dialect 1 => INTEGER, Dialect 3 => NUMERIC(18,0)

November 11, 2002 - v2.1.1.6:

Enhancements:

Scripting facility implemented. The IBLM Scripting Engine can be used to automate repetitive tasks in a script based way. A detailed script language reference is available in the Online-Help.
Enhanced statistical information about registered/unregistered database objects added.
A LEFT OUTER JOIN is used in the log data view now.
Recent databases are accessible through the "Recent Databases" menu item and additional via a new introduced alias drop-down box.
After analyzing the database, a warning message can be shown if there are database objects, which aren't registered for logging. This reminder will help you to keep the database fully registered, even when there are periodical DDL changes in your database. The warning message can be enabled/disabled in the Options-Dialog (tabsheet 'General').
The Expand/Collapse all Tables feature is now more intelligent. All nodes are expanded/collapsed and the focused node is still visible after that.
Analyzing the database, especially on slow remote connections, has been greatly improved.
TsiLang Components Suite has been upgraded to v5.2.
EMS QuickExport Package has been upgraded to v2.5.
Online-Help has been updated.
Some minor tweaks.

Bugfixes:

Bug fixed: Two problems fixed using "Delete All Record" without having the "Use ON DELETE CASCADE" option in the Prepare-Wizard checked.
Bug fixed: The usage of very large VARCHAR columns for Non-BLOB column logging has been fixed. Logging of columns is done now by using INSERT INTO statements directly, instead of executing a stored procedure. In prior IBLM versions there was an InterBase/Firebird exception "Request size limit exceeded" thrown. This seems to be an InterBase and Firebird issue, but the workaround in IBLM should fix this now.
Bug fixed: Case-Insensitive filtering works now as expected.

September 25, 2002 - v2.1.0.8:

Enhancements:

Support of English column names in the operation and column log table added. English column names will be enabled in the Prepare-Wizard by selecting the "Use English column names" option (per Default this option is not selected, so the Prepare-Wizard creates logging metadata as in prior versions). This version still works with prepared databases using German column names. Compatibility to older prepared databases is ensured behind the scenes. And there is no need to adapt the localization file "iblogmanager.sil".
Conditional logging added. If you want that data manipulation operations are only logged if a specific condition (e.g. USER <> 'REPL') is fulfilled, then define a condition, which encloses the logging trigger body. The conditions for each data manipulation operation can be specified in the 'Options' dialog (tabsheet 'Logging'=>'Conditional Logging').
Ascending/Descending indices on the operation log table can be activated/deactivated in the 'Database Properties' dialog. Deactivate both indices to speed up the insertion of logged data. Activate them if you want faster searching in logged data.
Transaction ID Logging support implemented. Firebird v1.5 and higher comes with a new context variable TRANSACTION_ID, which can be used to store the transaction id for each data manipulation operation. A new TRANSACTIONID column in the operation log table can be added in the Prepare-Wizard. Additional, transaction ID logging can be enabled/disabled in the 'Options' dialog (tabsheet 'Logging'=>'Additional Settings'). The transaction ID logging feature is pretty customizable, because the used context variable for the transaction ID can be defined in the Prepare-Wizard. So, if IB 7 comes with a similar context variable, then it's easy to use transaction ID logging with IB 7 too.
The "Open logged data when selecting treeview node" option is for new installations now checked per default.
EMS QuickExport data export package was upgraded to v2.3.
Some minor performance improvements.
Online-Help has been updated.

Bugfixes:

Bug fixed: Enable/Disable logging on dialect 3 (delimited identifiers) tables has been fixed.
Bug fixed: Registering a table with a compound primary key with more than 5 columns has been fixed. Only the first 5 columns in such a primary key are used when creating the logging trigger.
Bug fixed: The progress form is now always closed, even if there is an error occured.

March 26, 2002 - v2.0.5.3:

Enhancements:

IBO DML Caching support implemented. This feature can be enabled in the Prepare-Wizard, when preparing the database. The trigger and event name for the after insert trigger on the operation log table can be choosen in the Prepare-Wizard. The event-trigger can be activated/deactivated any time in the "Database Properties" dialog. The "Export Logging Metadata" feature was adapted to consider the possible IBO DML Caching Integration by exporting the source of the after insert trigger.
Table and column names (operation and column log) in a dialect 3 database can be logged as delimited identifiers enclosed by double-quotes. This ensures, that logged table and column names can be accessed without struggling with the delimited identifiers stuff. Logged delimited identifiers are also important for the proper IBO DML Caching default behaviour. The necessary option for this new feature can be found in the Options-Dialog (tabsheet 'Logging').
The usage of dialect 3 delimited identifiers inside the logging triggers has been optimized.
Visual improvement in the Prepare/Unprepare-Wizard. Different glyphs for Users and Roles are shown in the Users/Roles-Listbox.
Granted Users/Roles on logging metadata are pre-selected in the Unprepare-Wizard.
Additional filters (*.gdb, *.fdb, *.*) for selecting a database file in the Open-Dialog has been added.
Online-Help has been updated.

Bugfixes:

The appearance of the GUI when using German as internal language has been fixed.

February 27, 2002 - v2.0.4.3:

Enhancements:

A general VIEW with all logged data can be created/dropped when Preparing/Unpreparing a database. This view can be used for any tasks like querying logged data in your application in an easier way or when creating self written log data reports based on this view.
Important: Be aware that once a database was prepared with this view, prior versions of the Unprepare-Wizard will not remove this view! Actual or newer versions of IBLM 2.0 will run fine with prepared databases using prior versions of IBLM 2.0.4.3.
Logging metadata of a prepared database can easily exported into a SQL-script file. This file can be used to prepare a database without using the Prepare-Wizard on the destination database. See the menu item "File/Export Logging Metadata...".
Main menu and toolbar are now floatable and on different places in the main form dockable.
EMS QuickExport data export package was upgraded to v1.98.
Interbase Alias Manager (IBam) support was upgraded to v1.3a.
Localization files updated. Thanks to Kurt Bilde and Elias Todorovich!
Help-File updated.

Bugfixes:

Using AFTER [OPERATION] triggers makes the logging mechanism and logged data more reliable and consistent.
Primary and Foreign-Key definitions on logging tables are now stored in the metadata table IBLM$METADATA.

January 4, 2002 - v2.0.3.1:

Enhancements:

Localization package TsiLang Components Suite was upgraded to v5.0.0. There is also a new version (v2.0.2.21) of SIL-Editor for translating the external localization file (SIL-file) available. Check out http://www.sicomponents.com/download.html or the IB LogManager download section.
The maximal character length of logged primary key values for operation logging can be defined in the Prepare-Wizard. Now operation logging for records with primary key values larger than 20 characters is possible.

Bugfixes:

Bug fixed when viewing selected logged records using delimited identifiers as primary key columns.

November 29, 2001 - v2.0.3.0: First official release of IBLM 2.0 and IBLM 2.0 Viewer

Enhancements:

IB LogManager is now fully implemented with Jason Wharton's IBObjects.
Localization package TsiLang Components Suite was upgraded to v4.9.6. There is also a new version (v2.0.1) of SIL-Editor for translating the external localization file (SIL-file) available.
EMS QuickExport data export package was upgraded to v1.97.
Connecting to databases via IBam (Interbase Alias Manager) aliases implemented. Supported are IBam local and remote aliases. For detailed information about the Open-Source project IBam, please visit http://www.orcka.com
Explicit transaction handling when defining logged database objects gives much better performance on huge logging definition operations.
Logged data can be opened automatically when selecting the corresponding table or operation in the treeview. The necessary option can be found in the Options-Dialog.
Maintaining database metadata information was greatly improved. Now large operations like "Analyzing database", "Register All Tables", ... are running faster.
Only selecting "Date To" in the selection criteria gives all changes until the end of the "Date To" day.
ON DELETE CASCADE can be used to delete records with logged column data when logged operation records are deleted. This feature must be enabled in the Prepare-Wizard. ON DELETE CASCADE was introduced in IB 5.x, so don't use it with IB 4.x or prior!
Logging tables in the Prepare-Wizard now starts with "IBLM$" per default. Table "LOG_NOTATION" was renamed to "IBLM$METADATA", but databases which were prepared with prior versions of IBLogManager are STILL COMPATIBLE with v2.x! ONCE prepared with v2.x you CAN'T use v1.x anymore!
Export and Import of Logging Defintion implemented. Now you can easily export and import(execute) a logging definition script for many similar databases in one step.
User-defined names for logging metadata's primary and foreign keys are available in the Prepare-Wizard. The primary key for the table IBLM$METADATA is called PK_IBLM$METADATA and can't be changed in the Prepare-Wizard.
Source code of created stored procedures and triggers is now more readable, when viewing with any third-party tool.
Columns order, display width and sort order for each data grid is stored within "iblogmanager.cfg" and restored at program start.
Default logging metadata prefixes and postfixes can be defined in the Options-Dialog. These settings can be used to suggest user-defined logging metadata names in the Prepare-Wizard.
User-defined determination of trigger positions implemented. Following options are supported: "Fixed", "Next highest", "Calculated" and "Max"(Default: 32767).
Automatically registering all columns when registering an operation can be enabled/disabled. The proper setting can be found in the Options-Dialog.
Logging metadata notations in the Prepare-Wizard can be reloaded automatically with the latest used metadata names. See the Options-Dialog for proper settings.
Logging metadata notations in the Prepare-Wizard can be loaded/stored from/into a file (the file extension ".lmn" is used).
Logged data can be browsed (restricted) for the current connected user only.
Color definition in the Options-Dialog was extended with background color definition used in the logged data grid.
The usage of colors in the logged data grid can be restricted to user information in logged data. See the Options-Dialog for proper settings.
Some minor enhancements.

Bugfixes:

Bug fixed when selecting database paths including spaces in the Open-Dialog. Enclosed double quotes are now removed and the connection succeed.
Bug fixed when one tries to register an item in an unprepared database via double-click.
Bug fixed when double-clicking in the tree view without selecting any node.
Now editing nodes in the treeview isn't possible any more.
Selection criteria "Time To" is now initialized with "23:59:59" instead of "23:59:00" when IB LogManager is started the first time after installation.
Bug fixed in the Prepare/Unprepare-Wizard for dialect 3 databases when granting, revoking rights to/from Users/Roles with names like InterBase and Firebird or SQL related keywords.
Bug fixed minimizing modal windows.
Bug fixed calling print preview window two times and afterwards closing the preview window with an AV.
Bug fixed when switching between databases with different character sets. There was a problem using charset "NONE" after using a database with a charset different to "NONE" (e.g. ISO8859_1, ...). "NONE" wasn't correctly used at connect time.
Bug fixed when right "SELECT" on IBLM$METADATA to selected users/roles during prepare process wasn't granted.
Bug fixed when using a time separator in regional settings different to ":".
Some minor bugfixes.