ODBC QueryTool / News: Recent posts

Fix for a crash while saving *.sql files

• Partly rewrite of the settings streams. This was done on behalf of reports of corrupted settings after modifying some of them. The settings should be more
  stable now. Please remove old (corrupted) settings files from the "C:\USERS\<youraccount>\AppData\Roaming\EDO\ODBCQueryTool" directory to
  permanently get rid of this problem.</youraccount>
• Small fixes for the "ODBC Report" for a RDBMS datasource. Some strings where missing, due to the ANSI to Unicode conversion.
• Better SQLMigrate path from Oracle to PostgreSQL.
• Various small bugfixes, found by the strict compiling under /W4/WX settings.

• Upgraded to the newwest versions of the libraries (SQLComponents, BaseLibrary) that are no longer using the MFC-library from Microsoft. By using ISO std::string makes the program more stable and faster
• Dropped the suport of 32-Bits versions. Only 64-Bits versions are now released. This is in line with the general trend of software development, where 64-Bits is the standard and 32-Bits is becoming obsolete.
• Fixed a bug in the parsing of the ODBC SQL to fix the parsing of double quoted strings.This was specially for the usage of the "ODBC Text driver" in order to be able to do a: "SELECT * FROM "textfile.txt" or from a "*.csv" file. This is now working again.... read more

Various fixes for the discovery of databases with quoted identifiers.
(Firebird, MariaDB, Oracle, SQL-Server, PostgreSQL).
For most ODBC drivers only the SQLTables and SQLColumns work correctly.
Other functions such as the discovery of SQLPrimaryKeys, SQLForeignKeys,
SQLStatistics, SQLProcedures do not work for case senstive identifiers.

Also various fixes for the Info tree, so that we can now see the compelete
view, trigger, function and stored procedure source.

Quoted identifiers have been added to the system. OpenODBCQuerytool now understands the
identifiers (tablenames, viewnames, columns, indexes and such) that are stored in mixed
case format. So "FullName" and "Fullname" are different identifiers.
As a standard rule, all identifiers in one (1) case are understood to be non-quoted identifiers.
These will not be quoted, and standard nameing rules apply.
Per supported database platform the naming conventions are applied, beginning with Firebird.
Stay tuned for next service packs for other RDBMS'es that have case sensitive catalogs.
By default lMS-SQLServer and PostgreSQL can handel mixed cases. These work now out-of-the-box.
Orace, Informix, MySQL and MariaDB need extra work in their respective InfoDB classes.

Releasenotes 3.4.5

Fix for querying decimal number fields after a CLOB/BLOB column
Performance fix for retrieving columns after the last bound column
Unicode and SQLDate fixes
Fix for Firbird databases in getting procedures and procedure-parameters
Fix for PostgreSQL databases in getting procedures and procedure-parameters
For PostgreSQL databases it is now also possible to retrieve the procedure/function source text... read more

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<n> = variable<x>;"
4) Fixed a bug in the variables dialog (See menu: Script/Variables)</x></n>

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

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

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.... read more

Releasenotes 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.... read more

Releasenotes version 3.0.6

• Fixed problem with the "Table DDL" command. Table create statements are generated again.
• Fixed the problem with the F10 key (run current SQL command line). The program is now prevented
  from entering the 'Select main menu' state, after the pressing of this key.
  If you wish to use the main menu from the keyboard, use a single ALT key to go there.

Releasenotes version 3.0.5

• Fixed a bug when changing the default font in the settings when installed in "C:\Progam Files\Edo"
  this is the default location, so a lot of users will have this settup. The crash derived from the
  fact that there where no update rigths on the settings files.
  ODBCQueryTool now makes a copy of the setup files to the roaming profile of the user and afterwards
  works from this set of setting files. This also fixes the crash.
• Fixes for the saving of a changed text file when closing the application. A crash in the dialog
  that asks for the fact that the users wishes to save her/his work is solved.
• Fixed unwanted/unneeded message in the installer that same version is already installed
• Updates from support libraries to the latest versions (SQLComponents, StyleFramework, BaseLibrary)

Version 3.0.3 fixes a bug in setting a new font on the SQL Query results view.
You can now again set the desired font and fontsize.

This version is a complete rewrite of the main interface including the MFC Feature pack.

This version is a complete rewrite of the main interface including the MFC Feature pack.

Fixed various bugs in the handling of the MariaDB database in Oracle mode. Prefer to turn OFF the "Strict ODBC" handling in the general SQL settings for this database type, as the replacement SQL's work better for this database:

• Columns and other attributes of tables in other schema's can be discovered than just the currently active database schema.
• All database types are tested and some minor bugs in the handling of 'text' and 'longtext' columns have been fixed.

The new version fixes a few important bugs:

• Fixed a bug in the saving of the permanent file settings causing the application
  to crash after changing the file settings (e.g. tabs and space inserts).
  See: Menu / Text / File settings & information
• Fixed a bug in the parameter binding of a query with the ":variable<n>" settings
  for a "?" binding in a query.
  See the file "script_syntax.txt" for more details</n>
• Fixed a bug in the ":select on" command of the scripting syntax
  Columnnames and row values are now correctly written to the script output file,
  provided that you have used the ":file" command previously.
  See the file "script_syntax.txt" for more details

The source code of the SQLComponents are now replaced by a deployment ZIP file in the root directory of the project. The ZIP contains the include directory of that component and the four library files. For a full explanation, see: https://github.com/edwig/SQLComponents

Support for MariaDB has been added.

Various discovery methods for the info tree have been improved in speed for the Oracle database. The methods are:

• SQLColumns -> Discovery of all columns of a table
• SQLStatistics -> Discovery of all indices of a table
• SQLTablePrivileges -> Discovery of all table privileges
• SQLColumnPrivileges -> Discovery of all column privileges (NEW !)... read more

This version fixed nasty bugs in the login cycle. Here are the releasenotes:

• Fixed a bug in the startup cycle on the first discovery queries.
  It turned out that there where a few tables for in there that not all users
  have rights on to see (e.g. Oracle: "dba_db_links")
  Similar bugs for Informix, Firebird, PostgreSQL and SQLServer have been fixed
• Errors in SQL now turn up always with the erring SQL statement in them, so we
  can always see what went wrong.

Minor release that fixes the exception handling of errors from the SQL component to the editor.
Fixes strange error messages which only shows a line of sourcecode, to the 'real' SQL error.

• Fixed performance bug in starting of Oracle 12 database. Knocked of 6 seconds of each login for meta info of tables and catalogs.
• Oracle databases now also display all linked catalogs in the driver page
• Connection errors at login are now shown
• Upgraded to the latest MS-Windows 10 SDK build (17763)

Releasenotes version 2.1.0

In this release much work has been done for the object tree. The object tree
is now fully functional with the folllowing objects

• Tables
  • Table columns
  • Primary and foreign keys
  • Indices and table statistics
  • pecial (unique) columns not visible as table columns
  • Other table referencing this table
  • Triggers for the table
  • Sequences for the table
  • Granted rights on the table
• Views
• Catalog tables
• Synonyms
• Sequences
• Triggers
• Stored procedures... read more

In the 10th anniversary version of the Open ODBC Querytool a new info tree has been created. This tree makes it easier to find tables and views. See the FindingTables' page in the on-line help file.

Edo Huisman.

Version 1.5.0 is an imported update for all of you out there using MS-SQL Server.
This version repairs the decimal places problems with the DECIMAL/NUMERIC datatypes.