ODBC Query Tool Changelog

What's new in ODBC Query Tool 1.37

Feb 15, 2012
  • Minor change: The program now stores in its configuration file the main window position, size, and whether it was maximized or not when closing it, and restores these values on the next run.

New in ODBC Query Tool 1.36 (Jan 31, 2012)

  • In former versions, when executing a single SQL statement (with F5 or by clicking the ''Run SQL'' button), the program always appended a single semicolon at the end of the SQL statement before sending it to the ODBC driver. This caused some old database systems (Progress Database, in particular) to fail execution of the statement. Now single statements are sent without trailing semicolons.

New in ODBC Query Tool 1.35 Beta (Dec 27, 2011)

  • It fixes a somewhat important issue which affected long SQL statements (single statements longer than 2,000 characters were being truncated; the statement buffer is now 32 kbytes long).

New in ODBC Query Tool 1.34 Beta (Sep 26, 2011)

  • Added a new entry in the View menu to launch the ODBC Data Sources Administration control panel. This menu item will always launch the 32-bit version of said control panel, even under 64-bit operating systems, because ODBC Query Tool only works with 32-bit ODBC drivers.

New in ODBC Query Tool 1.33 Beta (Jul 16, 2011)

  • When executing a recordset-returning query that was taking too long, pressing the "Abort query" button would actually freeze the whole program because of a deadlock condition between the GUI thread and the ODBC worker thread. Fixed.

New in ODBC Query Tool 1.32 Beta (Jul 4, 2011)

  • Fixed a bug where trying to quit the program with a running query would check with the user if it's OK to discard the executing query, but would not check if there were unsaved tabs. Now it checks for both conditions when trying to exit the program.
  • Added a new output visualization mode, text-based output. This contains a plain text representation of query results output, as well as a easily visible error log in case of queries generating errors.

New in ODBC Query Tool 1.31 Beta (Jun 22, 2011)

  • SQL queries now run in their own thread of execution, so that the main screen keeps responsive to user input.
  • When a query or script is running, there's an "Abort query" button to interrupt the currently executing query or script. Partial results will be shown (if any).

New in ODBC Query Tool 1.30 (Jun 22, 2011)

  • Added capability to run single SQL statements or execute complete scripts with many statements. Pressing F5 will execute the SQL statement currently under the editing caret, F6 will execute the whole script. These options can also be accessed from the "File" menu.
  • After double-clicking column names on the schema tree to insert them on the current query, the editing caret is visible and the user can now start typing right away after inserting a column or table name.
  • Minor optimizations.

New in ODBC Query Tool 1.27 (Jun 22, 2011)

  • Added "Visit web site..." option in the help menu.
  • Fixed minor cosmetic details.

New in ODBC Query Tool 1.26 (Jun 22, 2011)

  • Sample queries when right-clicking a table name now have the correct syntax for Microsoft Excel.
  • Added "Check for updates..." option in the help menu. This will notify the user if there's a newer version than the current one, and optionally open the program's web page in the default browser.

New in ODBC Query Tool 1.25 (Jun 22, 2011)

  • Sample queries when right-clicking a table name now have the correct syntax for Oracle, Microsoft SQL Server and Microsoft Access. For example, the "Select first 100 rows from table" option results in "SELECT TOP 100 * FROM ;" in SQL Server and Access, "SELECT * FROM WHERE ROWNUM