Release 3.4.4

1. ODBCQueryTool now supports Oracle packages and can discover procedures and functions within packages and can retrieve the package sourcecode (if not wrapped)
2. A small bugfix for discovering procedures in the Firebird 3.x databases.

Release 3.4.3

1. The scripting :if command now has multiple operators: '=', '<>', '<', '>', '<=', '>='
2. The value of a variable can now be printed in the :print command to the output file
3. A variable can be assigned the value of another variable with ":variable = variable;"
4. Fixed a bug in the variables dialog (See menu: Script/Variables)

Release 3.4.2

Updated the libraries to the latest version. After a half year of testing: fixing a lot of small Unicode bugs.
Added the 'mustard' (yelow) and 'dark' themes
Fixed a bug in the object-discovery of the Firebird drivers. Columns of tables and procedure arguments are working again
Fixed a bug in the installer. Check on 'not-yet-installed' added

Release 3.4.1

Fixed a bug getting the database "Ping" from Firebird.
Also fixes a crash on that database after a few minutes.

Release 3.4.0

This version is dedicated to the conversion to Unicode 16.
The Unicode versions are still in early development stages.
For production environments you are still encouraged to choose for the (old fashioned)
ANSI/MBCS coding version.

You can make a choise from the following set of installers:

• 32 Bits ANSI/MBCS coding
• 32 Bits Unicode version
• 64 Bits ANSI/MBCS coding
• 64 Bits Unicode version

Release 3.3.1

Releasenotes 3.3.1

It is now possible to override the character set from the database by using one of two methods:

1. Reading the default character set from a system table (e.g. Firebird);
2. Choosing a character set directly from a list.

You can find this setting by navigating to the 'Text' menu, and then 'Permanent settings' and
then to the 'SQL' tab. There you will find the field 'Charset handling'. When choosing the third
option ('Use charset translation') the combobox for 'character set' will become active and you
can choose a character set.

Most notabely you can use this setting for RDBMS types that are not directly supported such as
for instance a 'SAP-Hana' database. Or for database types where the ODBC driver does not correctly
hands over the character buffer in UTF-16 form to the MS-Windows operating system.
Such as the Firebird ODBC driver 2.x

NOTE:Do NOT forget to reset this general setting when connecting to a different database that does
not adhere correctly to the ODBC standard! As it will bite you as it did me!! :-(

Release 3.3.0

In this release the free 'odbc-connection-string' feature is implemented (at last).
Connections can have the combination of "datasource" / "user" / "password".
Or a free connection string. In the latter case, only the 'datasource' name is
stored for the connection.

Optionally you can leave out the user name and/or the password name if a datasource
does not require these for security reasons. An MS-Access database or the MS-Excel ODBC driver
are examples of these.

There is a new button "Connection string" on the connection dialog, or you can use the
'Details' button to fill in a connection string to your liking.

Release 3.2.4

Releasenotes 3.2.4

At-Exec data at the end of a SELECT, or no NUMERIC columns gotten as a SQL_C_CHAR

Version 3.2.3

Fix for login dialog and the "production / development" switch
QueryRewriter no has knowledge of the 'UPDATE STATISTICS' statement

Release 3.2.2

• Fix for decimals in NUMERIC/DECIMAL datatypes.
• Fix for reading stored-procedures from SQL-Server
• Precision and scale are recalculated before syncing with the database
• Please note that the SQLMigrate tool has been removed from the SQLComponents library
  and now officially exists within this project.