JasonQuery - Release Notes

2026/09/29, version 0.96 #

[New Features]

1. Added a JasonQuery.db Recovery Key for disaster recovery

1.1. Windows Protected mode can now create a Recovery Key in advance. If the original Windows user profile, DPAPI binding, or operating-system environment is no longer available, the Recovery Key can be used to restore access to JasonQuery.db.

1.2. Recovery verifies the JasonQuery.db and Recovery Key pairing, preserves the existing logical database key, and rebinds it to the current Windows user protection. Recovery does not generate a new database key or re-key the database.

1.3. Incorrect, mismatched, or tampered Recovery Keys are rejected without incorrectly modifying the existing JasonQuery.db or its security metadata.

1.4. Recovery Keys can be regenerated or disabled. Regeneration invalidates the previous Recovery Key, and disabling recovery prevents the existing key from being used again.

1.5. Recovery Keys are specific to Windows Protected mode. Custom Password mode continues to use the user-defined password and does not use a Recovery Key.

1.6. Recovery also covers supported historical Storage V1 states. After successful recovery, JasonQuery can complete the Storage V1 → Storage V2 upgrade and use the new Storage V2 runtime on subsequent startups.

2. SQL History - Added automatic cleanup

2.1. Added SQL History automatic cleanup settings to the General tab in Options. The feature can be enabled independently for each database connection.

2.2. Automatic cleanup is disabled by default, so existing and newly created connections will not have SQL History deleted unless the user explicitly enables the feature.

2.3. When enabled, users can retain SQL History for the most recent 30, 60, 90, 180, or 365 days. Entries older than the selected retention period are automatically removed.

2.4. Automatic cleanup applies only to the current database connection and does not remove SQL History belonging to other connections.

2.5. Improved the Options settings persistence flow to significantly reduce the time required to apply large numbers of settings and ensure JasonQuery can close normally after SQL History automatic cleanup is enabled.

[Enhancements]

1. Modernized JasonQuery.db security and storage architecture

1.1. New JasonQuery.db storage uses Storage V2 with a SQLCipher 4-compatible format and an isolated Modern SQLite Runtime, protected by an independently generated logical database key.

1.2. An isolated Legacy Storage V1 compatibility runtime is retained so supported historical JasonQuery.db files can migrate directly to Storage V2. Migration does not create a plaintext staging database, and legacy and modern SQLite runtimes remain separated into different processes.

1.3. Added an explicit persisted storageFormatVersion contract. JasonQuery selects the correct runtime from the stored format version, fails closed for unknown versions, and does not guess the database format through provider probing or exception fallback.

1.4. Storage V1 → V2 migration preserves the existing security mode, logical database key, application schema, and saved connection information. A physical storage-format upgrade does not silently change the user's security configuration.

1.5. Added direct upgrade support for historical Default Password and Custom Password JasonQuery.db files. Legacy Default migrates to Windows Protected mode; Legacy Custom Password preserves the same user password while migrating to the new Custom Password protection. Incorrect passwords or migration failures stop startup without modifying the original JasonQuery.db.

1.6. Strengthened protection-mode switching and Custom Password changes with validated candidate databases, backups, transition journals, verification, and deterministic recovery for interrupted or ambiguous states.

1.7. Improved startup errors and backup/transfer guidance when Windows Protected data cannot be unlocked. JasonQuery.db and JasonQuery.security.json should be treated as a matched pair when backing up or moving an installation.

1.8. Consolidated the JasonQuery.db security and startup-error interfaces, retired legacy security dialogs, and updated English, Traditional Chinese, and Simplified Chinese wording to refer explicitly to JasonQuery.db so the messages are not confused with connected Oracle, PostgreSQL, SQL Server, or MySQL databases.

2. Improved security for saved database connection passwords

2.1. Existing DBInfo.Password values are automatically migrated from the historical per-field storage format to the new credential-storage model. Saved Oracle, PostgreSQL, SQL Server, and MySQL credentials remain usable after upgrade without requiring users to re-enter their passwords.

2.2. Saved connection passwords are now protected by the secured JasonQuery.db itself instead of applying the historical TripleDES/DES, DomainUser binding, and additional encoding to DBInfo.Password. Password writes also use parameterized SQL.

2.3. Preserved compatibility with the existing .jqc connection import/export format while strengthening temporary-file cleanup on success, wrong-password, and exception paths to reduce the risk of sensitive connection data remaining in the system temporary directory.

3. Runtime Logging - Improved TraceLogger v2 diagnostics and log management

3.1. Replaced the single, repeatedly overwritten JasonQuery.log file with a separate UTF-8 BOM CSV file for each logging session, allowing logs to be opened, filtered, and compared directly in Excel.

3.2. Added a fixed structured schema that records operation start and end events, parent-child relationships, execution duration, memory usage, database and object context, and error details to help identify performance bottlenecks and failure locations.

3.3. Improved thread-safe logging, nested-operation tracing, and logging lifecycle management. JasonQuery records the session completion status and releases the log file during a normal application shutdown.

3.4. Added session timestamps and Process IDs to log filenames to prevent collisions between application instances. Matching JasonQuery log files older than seven days are automatically removed, while recent and unrelated files are preserved.

3.5. Runtime logs do not intentionally record passwords, complete connection strings, SQL parameter values, or returned data rows. Before attaching a log to a public issue, users should still review database names, connection names, object names, and error messages that may appear in diagnostic fields.

4. Schema Browser - Improved tab content loading with Lazy Load

4.1. SQL Pane, Table/View Structure, the first 100 View rows, and the first 500 Table rows are now loaded only when the corresponding tab is opened for the first time, avoiding unnecessary queries and data processing.

4.2. The currently selected tab is preserved when switching database objects. If the new object does not support that tab, such as selecting a Function while Table Data is active, JasonQuery automatically returns to SQL Pane.

4.3. A successfully loaded object/tab combination is not queried again. If loading fails, the same tab can be retried after the cause has been corrected.

4.4. A wait message and busy cursor are displayed while JasonQuery retrieves information and prepares the Grid, providing clear feedback that loading is in progress.

4.5. Selecting a large Table no longer automatically retrieves its first 500 rows, reducing unnecessary waiting time. The data query runs only when the user explicitly opens the Table Data tab.

4.6. Added separate timing stages for SQL execution, KeyInfo, DataPage, data arrangement, and Grid formatting, while ensuring that an already loaded SQL script remains intact after other content tabs are opened.

5. Improved Windows version information and error diagnostics

5.1. Added a concise Windows version name to message-box captions and automatically omitted unavailable database version fields to prevent unnecessary separators.

5.2. Enhanced TraceLogger session logs with the full Windows edition, version, and build information while retaining the CLR version and process architecture for easier diagnosis of user-reported compatibility issues.

6. Improved Updater diagnostics and localized layout

6.1. Added an independent version identifier to the Updater window title so the running Updater build can be identified more easily. The Company Update Folder path field is also positioned dynamically after its localized label to prevent text overlap.

7. SQL Formatting - Updated the Microsoft SQL ScriptDOM component

7.1. Updated Microsoft.SqlServer.TransactSql.ScriptDom from version 180.78.1 to 180.102.0 to incorporate maintenance fixes and improve the compatibility and stability of the Microsoft SQL ScriptDOM formatting engine.

8. Improved JasonQuery.db internal architecture and regression coverage

8.1. Renamed internal JasonQuery.db security, storage-migration, and recovery classes, enums, namespaces, files, and tests from generic Database* identifiers to the clearer JasonQueryDb* naming, reducing ambiguity with user-connected databases and improving maintainability.

8.2. Significantly expanded regression coverage for Storage V1/V2 migration, runtime routing, security transitions, Recovery, connection-credential migration, and compatibility. The current complete automated test baseline contains 2,987 tests.

[Bug Fixes]

1. SQL Editor - Fixed tab file names when dragging multiple SQL files

1.1. Fixed an issue where only the last tab displayed the correct file name when multiple SQL files were dragged from Windows File Explorer into the editor. Each newly opened tab now completes file loading and initialization correctly and displays its corresponding SQL file name.

2. Connection Export

2.1. Fixed an issue where connection export could fail to use the current selections shown in the connection Grid. JasonQuery now determines the exported connections from the live checkbox state, preventing selected connections from being omitted or an incorrect number of connections from being exported.

2026/08/30, version 0.95 #

[Enhancements]

1. QueryForm - SQL Editor: Improved AutoComplete Error Feedback

1.1. When AutoComplete cannot retrieve suggestions because of an SQL error, a missing table, or another database error, a concise message directs users to SQL History for details.

1.2. The message is displayed only when the candidate query actually fails; no error is shown when no suggestions are available.

1.3. The message is cleared automatically after 15 seconds, or immediately after AutoComplete succeeds following an SQL correction.

2. Update System and Publishing Improvements

2.1. Added configurable update information sources

2.1.1. Added the JasonQuery Website, GitHub Releases, and Company Update Folder sources to the global Update Settings page.

2.1.2. Set the JasonQuery Website as the recommended update source.

2.1.3. The GitHub Releases source is temporarily unavailable and will be enabled after the official open-source releases are published.

2.1.4. Retained Company Update Folder support for enterprise, offline, and local-folder update environments.

2.1.5. Added validation for company update folders, metadata files, and saved update-source settings.

2.1.6. Expanded localized Company Update Folder help with IT administrator deployment steps, required files, local and UNC path guidance, and read-only access recommendations.

2.2. Improved the update-check workflow

2.2.1. JasonQuery now uses structured jasonquery-update.json metadata containing the version, release channel, download location, package size, and SHA-256 digest.

2.2.2. Added Production and Test release-channel selection rules to prevent incompatible updates and automatic downgrades.

2.2.3. Scheduled checks are marked as completed only after the metadata check succeeds; network, file, and JSON failures no longer incorrectly advance the schedule.

2.2.4. Improved localized update-source, error-reason, and metadata-location messages in English, Traditional Chinese, and Simplified Chinese.

2.2.5. Preserved the existing jq.txt format so previously deployed JasonQuery versions can continue using the legacy update-check mechanism.

2.3. Added a secure transactional update workflow

2.3.1. Update packages are verified using their expected size and SHA-256 digest before installation.

2.3.2. Added safe ZIP extraction that rejects directory traversal, absolute paths, symbolic links, duplicate paths, and unsafe Windows file names.

2.3.3. Updates are applied through a temporary Worker so Updater.exe can be safely replaced as part of the same transaction.

2.3.4. A verified backup is created before installation, with original file state, size, and SHA-256 information recorded in backup-manifest.json.

2.3.5. If an update fails, modified files are automatically restored and both backup and restored files are verified again using SHA-256.

2.3.6. User data, including JasonQuery.db, log, and backup content, is protected from update-package replacement.

2.3.7. The latest three fully verified update backups are retained.

2.4. Improved publishing and metadata automation

2.4.1. Official and test publishing workflows automatically read the version from JasonQuery.exe and classify it as a Production or Test release.

2.4.2. Publishing automatically calculates the release ZIP size and SHA-256 digest and generates jasonquery-update.json.

2.4.3. The legacy jq.txt file is generated at the same time to retain compatibility with existing installations.

2.4.4. Existing metadata is preserved if metadata generation or replacement fails, preventing a failed publication from damaging the currently available update information.

2.4.5. Remote metadata and package download URLs are required to use HTTPS.

2.4.6. Standardized official website, update metadata, download, release-note, and bug-report links on the canonical bare domain https://jasonquery.org/.

2.4.7. Added a Production-only IT administrator offline update package containing jasonquery-update.json, JasonQuery64.zip, and README-Company-Update.txt.

2.5. Improved Updater build and release integrity

2.5.1. Visual Studio builds now automatically copy Updater.exe and Updater.pdb to the corresponding JasonQuery Debug or Release output directory.

2.5.2. The release-package validator requires Updater.exe and Updater.pdb to be present in both the Release output and publication ZIP.

2.5.3. The Updater artifacts in the Release output and ZIP package are verified as byte-identical using SHA-256.

2.6. Completed full publishing and update regression testing

2.6.1. Added end-to-end coverage from an isolated old installation through metadata loading, ZIP payload resolution, package verification, safe extraction, transactional installation, verified backup, and restoration.

2.6.2. Verified that JasonQuery restarts successfully after an update and that Worker logs, the backup Manifest, and installed files are correct.

2.6.3. Verified that a tampered package is rejected for a SHA-256 mismatch before any installation content is modified.

2.6.4. Verified that a package containing protected paths such as JasonQuery.db is rejected before backup creation or installation changes.

2.6.5. Verified that JasonQuery.db and user content under log and backup remain unchanged throughout update and restoration operations.

2.6.6. Completed regression testing of the official publishing workflow, Release package validation, actual Updater execution, and the already-running-latest-version UI state.

[Bug Fixes]

1. QueryForm - SQL Editor: AutoComplete

1.1. Fixed an issue where, when a derived table or subquery selected identically named columns from different source tables, the candidate list triggered by an alias followed by a period—for example, demo.—could incorrectly reuse the metadata of the last matching column for every item. Each candidate now preserves its correct Source Table, data type, and nullability metadata.

2. Fixed the UTF-8 BOM encoding status display

2.1. Fixed an issue where UTF-8 files containing a byte order mark were shown as “UTF-8” in the status bar. They are now correctly displayed as “UTF-8 BOM”, while UTF-8 files without a BOM continue to display as “UTF-8”, allowing the file encoding format to be identified accurately.

3. Fixed an issue where one-click update could fail to download the update package.

3.1. Improved the Updater’s asynchronous download lifecycle and error handling, and added package size and SHA-256 verification before extraction. If one-click update fails in JasonQuery v0.94 or earlier, use the manual download link in the Check for Updates window to complete the update.

2026/08/20, version 0.94 #

[Enhancements]

1. Improved SQL formatting and list layout

1.1. When Oracle uses Hogimn SQL Formatter, SELECT, FROM, WHERE, GROUP BY, HAVING, ORDER BY, JOIN, ON, AND, and OR now follow a more conventional Oracle-aligned layout.

1.2. Added a shared List Items Per Line setting with values from 1 to 10 and a default of 3. It applies to Hogimn SQL Formatter for Oracle, PostgreSQL, SQL Server, and MySQL, as well as Microsoft SQL ScriptDOM Formatter for SQL Server.

1.3. The List Items Per Line setting applies to SELECT, GROUP BY, ORDER BY, and nested queries. Both SQL Server formatter engines now support the same setting.

1.4. PostgreSQL, SQL Server, and MySQL retain the existing clause layout of their respective formatter engines while redistributing list items according to the configured value.

1.5. Strengthened semantic safety for list formatting to prevent incorrect splitting of function arguments, IN lists, STRING_AGG, window functions, comments, string literals, and quoted identifiers while continuing to honor the Inline Block Max Length setting.

1.6. Improved spacing between multiple SQL statements so that both Hogimn SQL Formatter and Microsoft SQL ScriptDOM Formatter correctly apply the Blank Lines Between Statements setting.

2. Main Form and SQL Editor Operations

2.1. Simplified the Main Form menu by removing the Edit menu, which duplicated the SQL editor’s context menu. Save and Save As on the File menu now operate directly on the active SQL editor tab, with consistent Ctrl+S and F12 shortcut behavior.

[Bug Fixes]

1. Query Form - Query Execution

1.1. Fixed an issue where the query timeout setting was not fully applied to non-query commands. Single and batch data modification commands for Oracle, PostgreSQL, SQL Server, and MySQL now honor the configured query timeout.

1.2. Fixed an issue where pressing Space after WHERE, AND, or OR in an UPDATE statement did not trigger SPACE AutoComplete or display column suggestions for the target table.

1.3. Fixed an issue where cancelling a DML statement waiting for a database lock could incorrectly display the transaction as not yet committed or rolled back. If no transaction was pending before execution, the cancelled transaction is ended; any transaction that was already pending is preserved.

2. Minor bug fixes and improvements

2026/08/10, version 0.93 #

[Enhancements]

1. Query Form

1.1. Improved locking-query syntax detection to prevent FOR UPDATE clauses or locking hints contained in comments, string literals, or quoted identifiers from being incorrectly recognized as actual locking queries.

2. Options Form - Improved editor operations

2.1. Added context menus and common keyboard shortcuts to the Auto Replace, Keywords, SQL to Code, and SQL Formatter editors. Editable areas support Undo, Redo, Cut, Copy, Paste, Delete, and Select All, while read-only preview areas are limited to Copy and Select All.

3. Improved database version information management and display

3.1. Separated database version information into distinct responsibilities for legacy compatibility checks, display and diagnostic information across all four supported databases, and SQL Server-specific capability detection. Version display formats for Oracle, PostgreSQL, SQL Server, and MySQL are now standardized, with 24 new unit tests covering version parsing, connection switching, state cleanup, and SQL Server create-script compatibility.

4. Error Message Dialogs – Enhanced Title Information

4.1. Error message dialog titles now display the JasonQuery version, database type, and database version, making it easier for users to provide complete environment information when reporting issues and improving troubleshooting efficiency.

5. Modernized the SQL formatting engines

5.1. Replaced the legacy Poor Man's T-SQL Formatter with Hogimn SQL Formatter and the Microsoft SQL Server Transact-SQL ScriptDOM-based formatter, improving formatting compatibility and stability across supported database dialects.

5.2. Oracle, PostgreSQL, and MySQL now use Hogimn SQL Formatter. SQL Server recommends Microsoft SQL ScriptDOM by default while allowing users to switch to Hogimn SQL Formatter.

5.3. Added settings for formatter engine selection, indentation size, and blank lines between SQL statements, shared by both the formatter preview and SQL editor.

5.4. Strengthened token-level semantic validation to prevent formatting from unintentionally changing identifiers, string literals, comments, or the original meaning of SQL statements.

5.5. Removed PoorMansTSqlFormatterLib and its legacy dependencies, simplifying JasonQuery's build and release packages.

6. Improved color picker component and interaction safety

6.1. Replaced the legacy custom ColorPicker used by Connection, Color Converter, Options, and Schema Browser with Cyotek Windows Forms Color Picker.

6.2. Removed the legacy ThemeColorPicker, ThemeColorPickerWindow, and related resources, and adopted an MIT-licensed NuGet component with third-party license notices.

6.3. Color changes are applied only after selecting OK; selecting Cancel preserves the existing settings and helps prevent unintended changes.

[Bug Fixes]

1. Minor bug fixes and improvements

2026/08/06, version 0.92 #

[New Features]

1. Query Form

1.1. Added a safe execution mechanism for locking queries, supporting Oracle, PostgreSQL, and MySQL SELECT ... FOR UPDATE / FOR SHARE syntax, as well as the corresponding SQL Server locking hints.

1.2. A safety warning and confirmation prompt are displayed before executing a locking query, reminding users to review the WHERE condition and the potential impact of database locks.

1.3. JasonQuery automatic paging is not applied to locking queries. Schema information and query results are retrieved through a single data-reader execution to prevent the same locking SQL statement from being executed more than once.

1.4. After a locking query is executed successfully, JasonQuery keeps the current database connection and transaction open and displays the pending Commit or Rollback status, allowing the user to decide whether to commit or roll back the transaction.

1.5. If a locking query is cancelled after execution has already started, JasonQuery conservatively retains the Pending Transaction status to avoid overlooking locks that may already have been acquired by the database.

2. Schema Browser Form & Query Form

2.1. Right-click a column name to quickly perform column operation such as add. The generated SQL can be viewed in SQL History.

[Bug Fixes]

1. Schema Browser Form

1.1. Fixed an issue where the Comments column on the Table Structure tab could display incorrect PostgreSQL column comments, ensuring that each table column now shows the correct comment.

2. Query Form

2.1. Fixed an Oracle error-position highlighting issue where, if a SQL statement started with comments, the highlighted error position could incorrectly point to the comment text.

3. Table Operations - Rename

3.1. Fixed an issue in Oracle and PostgreSQL table renaming where changing only the letter case of a table name could prevent the DDL statement from being generated and leave the SQL preview blank. JasonQuery now preserves the letter case entered by the user and keeps the Execute button state synchronized with the SQL preview.

4. Schema Browser Form – Fixed SQL Server version compatibility issues when generating table creation scripts

4.1. Fixed an error that occurred when generating table creation scripts on SQL Server 2016 because the unsupported optimize_for_sequential_key system column was queried. JasonQuery now detects SQL Server version capabilities and omits the unsupported query column and OPTIMIZE_FOR_SEQUENTIAL_KEY index option on versions earlier than SQL Server 2019.

5. Minor bug fixes and improvements

2026/07/31, version 0.91 #

[New Features]

1. Query Form

1.1. Added a message pane at the bottom of the form to display JasonQuery operation tips. The pane closes automatically after 2 minutes or after SQL execution.

1.2. Added enhanced diagnostics for PostgreSQL error code 22001 to identify possible columns whose data length exceeds the defined limit.

1.3. Added column heading enhancements for SELECT query results in the data grid.

1.3.1. Purple heading text indicates a primary key column; blue heading text indicates a column that does not allow null values.

1.3.2. When the mouse hovers over a column heading, JasonQuery displays basic column information and the source table.

1.4. Added pending transaction reminders for data modification SQL, such as UPDATE or DELETE.

1.4.1. If there is no Commit or Rollback for more than 5 minutes, JasonQuery displays a reminder and prompts the user to choose an action.

1.4.2. If another 5 minutes pass without Commit or Rollback, JasonQuery displays the reminder again to help reduce the risk of table locking.

1.4.3. A pending transaction warning is also displayed at the bottom of the Main Form, indicating that Commit or Rollback is still required.

1.5. Added display control for large text columns.

1.5.1. The display length can be specified in Options. The default value is 50 characters, and truncated content is marked with "(truncated...)" at the end.

1.5.2. To view the full content, double-click the cell to open the Cell Viewer, which displays the complete text.

1.5.3. The data grid no longer renders the full content of large text columns by default, reducing memory and rendering pressure.

2. Schema Browser Form

2.1. Completed schema object listing for all supported databases, including Table, View, Function, Trigger, Index, Package, and Procedure where supported by the database.

3. SQL History Form

3.1. Starting from connection initialization, JasonQuery records all internal SELECT queries actively sent to the database, and the complete SQL statements can be viewed in this form.

3.1.1. Records SELECT queries used to collect database schema information, including Table, View, Function, and related column metadata for Table and View objects.

3.1.2. Records SELECT queries required by AutoComplete, such as retrieving all columns of a table or all columns represented by an alias name.

3.1.2.1. For PostgreSQL, when the Savepoint option is enabled, JasonQuery executes a Savepoint before AutoComplete SELECT queries and releases it after the query to avoid interrupting the existing transaction.

3.1.2.2. For example, if the AutoComplete data grid is expected to appear but does not, the SQL History Form can be used to review which SELECT SQL JasonQuery executed and whether that SQL caused an error.

4. IconLibrary.dll

4.1. Centralized most icon resources into IconLibrary.dll to reduce icon management and maintenance overhead.

5. Connection Form - Running Logs

5.1. Added the "Running Logs" option to record JasonQuery operations that are explicitly marked for logging in the code.

5.2. Running Logs can be enabled manually in the Connection Form, and logging starts after the connection button is clicked.

5.3. JasonQuery can also be started through JasonQuerySaveRunningLogs.bat, which enables logging from the moment JasonQuery.exe starts. In this mode, the "Running Logs" option is automatically checked and disabled.

5.4. The log file is automatically created in the Log folder under the JasonQuery.exe directory, for example: .\Log\JasonQuery.log

6. Automatic update detection for release and preview versions

6.1. For preview versions under the same release version, such as 0.91.xx, JasonQuery compares the current version number with the latest version published online. If 0.91.yy is detected and yy is greater than xx, a prompt is displayed and the user can decide whether to update.

6.2. If the next release version is detected, such as 0.92.00, a release update prompt is displayed and the user can decide whether to update.

6.3. If issues are found after updating to the latest preview version, Updater.exe can be opened from [Help] > [Update Now] to update back to the release version. The same approach can also be used to switch from the release version to the preview version.

[Enhancements]

1. Localization

1.1. Optimized localization wording. Some technical terms are now displayed in English, such as Commit, Rollback, and Schema.

1.2. Shortened some form text and moved detailed descriptions to tooltips or nearby help buttons.

2. Schema loading

2.1. Improved startup performance when collecting and loading schema objects such as Table, View, Function, and Trigger for all supported databases.

3. AI-assisted refactoring

3.1. Centralized query result schema metadata returned by Devart into context objects so it can be reused by features such as column heading popups.

3.2. Reduced the size of God Form and God Class code by extracting responsibilities into more focused components.

3.3. Consolidated duplicated or similar logic into shared methods and helpers for easier maintenance.

4. Connection Form - Main Form icons

4.1. Removed some icons that may have licensing concerns for better license compliance.

4.2. Recreated JasonQuery's custom icons.

5. Main Form

5.1. Removed the automatic disconnect feature. Pending transaction reminders are now used instead.

6. Error messages

6.1. Enhanced error messages for both handled and unhandled exceptions. When available, the message now includes the source code file and line number where the error occurred, making issue reporting easier and helping identify the possible cause more quickly.

7. Code maintainability

7.1. Updated many legacy variable names to better align with modern naming conventions, improving code readability and maintainability.

[Bug Fixes]

1. Query Form

1.1. Fixed an issue where the error position indicator could be offset when SQL execution errors occurred in Oracle and PostgreSQL.

1.1.1. Oracle: Fixed error position indication for ORA-00942, "table or view does not exist."

1.1.2. PostgreSQL: Fixed error position indication for 42P01, "relation does not exist", and 42703, "column does not exist."

1.1.3. PostgreSQL: Fixed error position highlighting for 42501 privilege-related errors by locating database object names in messages such as "permission denied" and "must be owner of".

2. Query Form

2.1. Fixed an issue where trailing spaces in Oracle CHAR column query results could be automatically trimmed by Devart. JasonQuery now pads the value with spaces to the defined column length to preserve the fixed-length CHAR content.

3. Minor bug fixes and improvements

2025/02/12, version 0.90 #

[New Features]

1. Schema Browser Form

1.1. Right-click a table name to quickly perform table operations such as comment, drop, rename, and truncate. The generated SQL can be viewed in SQL History.

1.2. Right-click a column name to quickly perform column operations such as comment, drop, and rename. The generated SQL can be viewed in SQL History.

1.3. For Oracle, list Package Object contents.

2. Query Form

2.1. Added "F8 Tab List": all tab names are displayed. Double-click to quickly switch to the specified tab

2.2. Added "F9 SQL List": lists all SQL statements in the editor, grouped by type

2.3. Right-click a table name in the schema information area to quickly perform table operations such as comment, drop, rename, and truncate. The generated SQL can be viewed in SQL History.

2.4. Right-click a column name in the schema information area to quickly perform column operations such as comment, drop, and rename. The generated SQL can be viewed in SQL History.

2.5. Added a button to the query result data grid toolbar to list all column names. Double-click a column name to quickly switch to that column.

3. Connection Form

3.1. Added "Exit" and "Update Now (One-click Update)" buttons

[Bug Fixes]

1. Minor bug fixes and improvements

2024/10/16, version 0.89 #

[New Features]

1. Schema Browser Form - Added "Edit Table Data": users can add, update, and delete data directly in the grid for Oracle, PostgreSQL, SQL Server, MySQL, and MariaDB.

1.1. Automatically generates SQL statements for modified data.

1.2. When the mouse hovers over a modified cell, the original and modified values are displayed.

1.3. When changes are applied, the executed SQL is automatically written to SQL History.

1.4. Numeric cells only accept numeric input, and invalid characters such as letters are automatically ignored.

1.5. Date cells only accept numeric input, and the allowed values are constrained by valid year, month, day, hour, minute, and second ranges.

1.6. Text cells automatically limit input according to the defined column length.

2. Query Form

2.1. For query result columns that do not allow null values, the column heading text is displayed in bold blue.

[Enhancements]

1. Query Form

1.1. Changed the layout from a top/bottom split to a left/right split

1.2. Added "Show Column Comments": when a SELECT statement is executed, JasonQuery attempts to display comments for each column.

2. Schema Browser Form

2.1. Improved Oracle table Create Script formatting.

3. SQL History Form

3.1. Added the "Operation Object" column to help identify the source of each operation.

3.2. Added the "Operation Serial Number" column to help identify operations from the same execution, such as batch UPDATE or DELETE SQL.

[Bug Fixes]

1. Minor bug fixes and improvements

2024/05/09, version 0.88 #

[New Features]

1. Create Table Form (for Oracle) - [Tools] > [Create Table]

1.1. Provides an interactive interface for creating a new table and automatically generates the Create Table script.

2. Options Form - Enter key movement direction

2.1. The default value is "Down"

[Enhancements]

1. Main form - [File] > [Database Connection - View Mode]

1.1. Quickly view information related to database connections

[Bug Fixes]

1. Fixed the millisecond display for Oracle TIMESTAMP columns.

2. Minor bug fixes and improvements

2024/03/15, version 0.87 #

[New Features]

1. Main Form

1.1. Added a Traditional Chinese version of the Release Notes page: http://www.jasonquery.org/releasenotes_cht.html It can be opened from [Help] > [Release Notes].

1.2. Added "Color Picker" to Assistant.

2. Query Form

2.1. Added the "Periodic Backup" feature. The default backup interval is 7 seconds and can be changed in [Tools] > [Options] > [Global].

2.1.1. Automatically backs up modified but unsaved content. The next time JasonQuery is opened, it automatically restores the last unsaved content.

2.2. Added "Execute Current Line": automatically selects and executes the SQL statement on the current line. Shortcut key: Shift+Enter.

2.3. Added the "Remove Trailing Blanks" button to remove excess trailing spaces from each selected SQL line.

[Enhancements]

1. Main Form

1.1. The Release Notes page URL was changed to http://www.jasonquery.org/releasenotes.html

1.2. The Report Bugs page URL was changed to http://www.jasonquery.org/reportbugs.html

2. Updater.exe

2.1. The update source was changed from jasonquery.000webhostapp.com to www.jasonquery.org.

2.1.1. Free hosting is often blocked by company networks, which can cause update failures, so the update source was moved to paid hosting.

[Bug Fixes]

1. Minor bug fixes and improvements

2024/02/27, version 0.86 #

[New Features]

1. Schema Browser Form - In the "Data" tab, double-click a BLOB, bytea, or Binary column.

1.1. Load a file into a BLOB, bytea, or Binary column.

1.2. Set the column value to null.

2. Connection Form

2.1. Added "Query Timeout" setting

2.2. Customize the icon displayed by JasonQuery for the connection, making it easier to identify the database from the taskbar when multiple JasonQuery instances are open.

3. Query Form

3.1. Added two buttons: Zoom In and Zoom Out.

3.2. Added the "Query Timeout" setting. The value can be adjusted temporarily here.

4. Main Form - Added "Assistant" to the main menu.

4.1. Quickly launch commonly used applications, such as Calculator, Paint, Notepad, and File Explorer.

4.2. Quickly switch to commonly used paths, such as Desktop, Temp, and Startup.

4.3. ASCII Table

[Enhancements]

1. Allow multiple Schema Browser Form to be opened.

2. Refined all icons used by JasonQuery, including main menu, context menu, and toolbar icons.

[Bug Fixes]

1. Minor bug fixes and improvements

2023/10/02, version 0.85 #

[New Features]

1. Query Form - Right-click menu of SQL Editor

1.1. Automatically detects the word under the mouse cursor. If it is a table or view, the context menu can open Schema Browser Form or Generate SQL Statement Form directly to quickly view related information.

[Enhancements]

1. Connection Export Form

1.1. Allows users to select which connection information to export.

[Bug Fixes]

1. Minor bug fixes and improvements

2023/09/21, version 0.84 #

[New Features]

1. Blob/Hex Viewer Form

1.1. This feature can be opened from [Tools] > [Blob/Hex Viewer], or by double-clicking a BLOB, bytea, or Binary column and opening it through the Cell Viewer.

1.2. Supports viewing and editing blob, bytea, or binary columns, or a specified file.

[Enhancements]

1. Cell Viewer Form

1.1. Added four buttons: First, Previous, Next, and Last.

1.2. For blob, bytea, and binary columns, the Blob/Hex Viewer can be opened to view or edit the column's hexadecimal content, with support for Save and Save As.

2. SQL History Form

2.1. Right-click in the query result area to paste the SQL statement from the current row into the Query Form.

3. Schema Browser Form - View Top 100 Rows

3.1. Double-click a cell to open the Cell Viewer Form.

[Bug Fixes]

1. Query Form - for query results

1.1. If query results are manually filtered, only the filtered results are exported instead of all query results.

1.2. If the column order is manually changed, the adjusted column order is used during export instead of the original query result order.

2. Minor bug fixes and improvements

2023/07/20, version 0.83 #

[New Features]

1. Schema Browser Form

1.1. Added the "Find and Replace" feature.

2. SQL History Form

2.1. Added the "Find and Replace" feature.

[Enhancements]

1. Query Form

1.1. Rewrote the "Find and Replace" feature.

[Bug Fixes]

1. Query Form & Updater.exe

1.1. Minor bug fixes and improvements

2023/03/24, version 0.82 #

[New Features]

1. Query Form - Added "Show Grouping Row"

1.1. Users can drag columns into the grouping area. The data grid will sort the data by those columns at runtime.

[Bug Fixes]

1. Minor bug fixes and improvements

2023/02/21, version 0.81 #

[New Features]

1. Connection Form - Added a "Password Protection for JasonQuery.db" button.

1.1. Users can customize the password used to protect the contents of JasonQuery.db.

1.2. After setting a custom password, users must enter it manually every time JasonQuery starts.

[Bug Fixes]

1. Minor bug fixes and improvements

Other:

1. Starting with version 0.81, the x86 version is no longer maintained.

2022/11/01, version 0.80 #

[New Features]

1. Connection Form - Added "Export" and "Import" buttons.

1.1. Users can specify a password to encrypt and export all connection information.

1.2. Users can import encrypted connection information.

[Enhancements]

1. Query Form - Auto List Members

1.1. When no alias is specified, JasonQuery attempts to list all column information.

[Bug Fixes]

1. Minor bug fixes and improvements

2022/10/05, version 0.79 #

[Enhancements]

1. Query Form - for "Auto-List Members" & "Auto-Complete"

1.1. When users enter a keyword, matching words that start with that keyword are listed at the top.

2. Updater.exe

2.1. Added the "Update (Preview Version)" button, supporting one-click update to a preview version.

2.2. If JasonQuery is detected as running, the updater prompts the user to automatically force close JasonQuery.

3. Generate SQL Statement Form

3.1. This feature can be opened from [Tools] > [Generate SQL Statement].

3.2. Users can specify a table or view to generate SQL statements.

3.3. Table and view names can be searched by keyword.

3.4. For INSERT statements, users can choose "Display as Parameter", which is useful when applying the SQL in code.

[Bug Fixes]

1. Query Form

1.1. Fixed an issue where the SQL Server DATE type was displayed as DATETIME.

1.2. Minor bug fixes and improvements

2022/09/06, version 0.78 #

[New Features]

1. Query Form

1.1. Added "Auto Complete" function

2. Options Form - Auto Complete

2.1. Users can enable or disable Auto Complete. It is enabled by default.

[Bug Fixes]

1. Query Form - SQL Editor

1.1. Minor bug fixes and improvements

2022/08/23, version 0.77 #

[New Features]

1. Connection Form - PostgreSQL/SQL Server/MySQL/MariaDB

1.1. The Database field supports Auto Complete.

[Enhancements]

1. Query Form - SQL Editor

1.1. Supports Auto List Members for USE, SELECT, INSERT, UPDATE, and DELETE statements.

1.2. Auto List Members does not load all database schemas when there are too many databases, avoiding long loading times.

[Bug Fixes]

1. Query Form - SQL Editor

1.1. Minor bug fixes for Auto List Members.

2022/08/16, version 0.76 #

[New Features]

1. Query Form

1.1. Added "Auto list members" function

2. Options Form - Query Editor

2.1. Users can enable or disable Auto List Members. It is enabled by default.

3. Main Form - PostgreSQL/SQL Server/MySQL/MariaDB

3.1. Added "Switch Database" function

[Bug Fixes]

1. Main Form

1.1. Minor bug fixes and improvements

2. Query Form - SQL Editor

2.1. Minor bug fixes and improvements

2022/07/26, version 0.75 #

[Bug Fixes]

1. Query Form - SQL Editor

1.1. Minor bug fixes and improvements

2022/05/22, version 0.74 #

[New Features]

1. Query Form

1.1. Schema Browser Form: added context menu functions.

1.2. Paging Query: added "Appending Queries".

1.3. SQL Server and MySQL: added support for the USE statement. Users can execute "USE database;" to switch to another database.

2. Schema Browser Form

2.1. Added right-click menu functions

3. Generate SQL Statement Form

3.1. This feature can be opened from [Tools] > [Generate SQL Statement].

3.2. Tables and views: SQL statements are generated automatically.

4. Options Form

4.1. Added the "Appending Queries" setting. It is enabled by default.

2022/04/06, version 0.73 #

[Enhancements]

1. Query Form - SQL Server

1.1. Added support for DECLARE syntax in SELECT, INSERT, UPDATE, and DELETE statements.

1.2. Improved SQL error positioning.

[Bug Fixes]

1. Connection Form - PostgreSQL/SQL Server/MySQL/MariaDB

1.1. Rewrote the database connection string builder.

2022/03/28, version 0.72 #

[New Features]

1. Connection Form

1.1. Oracle: added the Unicode option.

1.2. SQL Server: added the Port option.

1.3. MySQL: added the Port option.

2. Query Form

2.1. Added export to JSON format.

[Bug Fixes]

1. Minor bug fixes and improvements

2022/03/14, version 0.71 #

[New Features]

1. Main Form

1.1. Localization: added Simplified Chinese.

1.2. Display the database version number in the status bar.

[Bug Fixes]

1. Minor bug fixes and improvements

2022/02/28, version 0.70 #

[New Features]

1. Query Form

1.1. Added export to XML format.

2. If JasonQuery.db does not exist, create it and display initial information.

[Bug Fixes]

1. Minor bug fixes and improvements

2022/01/23, version 0.69 #

[New Features]

1. Oracle

1.1. Oracle Server 21c is supported.

2. PostgreSQL

2.1. PostgreSQL Server 14 is supported.

3. Query Form - Data Grid context menu

3.1. Added "Copy Column Name".

[Bug Fixes]

1. Oracle

1.1. Fixed a bug in OracleScript when declaring multiple functions or procedures in a WITH clause.

1.2. Fixed a bug when connecting via a DNS name in an IPv6 network in Direct mode.

1.3. Fixed an ORA-12899 error when using parameters with an Oracle 12 server in Direct mode.

Updated Component:

1. Devart.Data.dll - 5.0.2834.0

2. Devart.Data.Oracle.dll - 9.15.1410.0

3. Devart.Data.PostgreSql.dll - 7.23.2042.0

4. Devart.Data.SqlServer.dll - 3.0.680.0

5. Devart.Data.MySql.dll - 8.20.2042.0

2022/01/09, version 0.68 #

[Bug Fixes]

1. PostgreSQL

1.1. Fixed "column p.proisagg does not exist" when retrieving function and trigger names in PostgreSQL 11 or later.

2. Minor bug fixes and improvements

2021/12/19, version 0.67 #

[Bug Fixes]

1. Schema Browser Form

1.1. Minor bug fixes for filter function

2. Minor bug fixes and improvements

2021/10/31, version 0.66 #

[Bug Fixes]

1. Query Form - SQL Editor

1.1. Fixed a bug in Cut / Ctrl+X.

2. Minor bug fixes and improvements

2021/10/24, version 0.65 #

[Enhancements]

1. Query Form

1.1. Combined "Export Data to Excel" and "Export Data to CSV" into "Export Data to File (Excel/CSV)".

[Bug Fixes]

1. Query Form

1.1. Fixed numeric sorting.

2. Query Form - Data Grid

2.1. Determines whether a WITH clause is a SELECT statement.

3. Minor bug fixes and improvements

2021/10/04, version 0.64 #

[New Features]

1. Query Form - Data Grid

1.1. Added "Single Record Viewer" function

2021/09/29, version 0.63 #

[New Features]

1. Query Form - SQL Editor

1.1. Added support for GBK encoding.

[Enhancements]

1. Schema Browser Form - Oracle/PostgreSQL/SQL Server/MySQL/MariaDB

1.1. Added "View Top 100 Rows" for tables and views.

[Bug Fixes]

1. Minor bug fixes and improvements

2021/09/12, version 0.62 #

[New Features]

1. Added support for MySQL and MariaDB servers, including Schema Browser.

[Enhancements]

1. Main Form

1.1. The database icon is displayed at the bottom left, making it easier to identify the current database.

New Component:

1. Devart.Data.MySql.dll - 8.19.1944.0

2021/09/05, version 0.61 #

[New Features]

1. Query Form - Data Grid

1.1. Added Average, Count, and Sum calculations based on the selected range.

1.2. Added "Export All Data to Clipboard" and "Export Current Row Data to Clipboard".

2021/08/29, version 0.60 #

[Bug Fixes]

1. Query Form - Copy as Query Condition

2. Fixed an ORA-00918 error thrown by OracleCommand.ExecutePageReader().

2.1. The issue occurred in Oracle 12c or later when a SQL query returned multiple columns with the same name, such as from multiple result sets, multiple tables or views, or subqueries.

Updated Component:

1. Devart.Data.dll - 5.0.2736.0

2. Devart.Data.Oracle.dll - 9.14.1312.0

3. Devart.Data.PostgreSql.dll - 7.20.1944.0

4. Devart.Data.SqlServer.dll - 3.0.582.0

2021/08/01, version 0.59 #

[Enhancements]

1. Query Form - Data Grid (functions related to "Copy/Copy As Query Condition/...")

2. Schema Browser Form - Table Structure ("Select All" function)

2021/06/28, version 0.58 #

[Enhancements]

1. Query Form - Cell Viewer (subform)

1.1. Minor bug fixes for Dark Mode.

2. Schema Browser Form

2.1. Added SQL Server support, excluding SQL Server 2000.

2021/06/16, version 0.57 #

[Enhancements]

1. Query Form - Variables (subform)

1.1. Added Select All, Copy, and Word Wrap buttons for the Preview feature.

2. Schema Browser Form - Rewrite

2.1. Improved form loading speed.

2.2. Added the Table Structure feature.

2021/06/03, version 0.56 #

[Enhancements]

1. Query Form - Export all data to Excel

1.1. If the number of rows exceeds 65,535, the file type is automatically switched to "Excel 2007 (xlsx)".

2. Query Form - Disconnect automatically

2.1. After executing a query SQL statement, the connection is automatically disconnected if Commit or Rollback is not required.

2.2. JasonQuery will automatically reconnect to the database before the next SQL statement is executed.

3. Main Form - Add to "My Favorite"

3.1. Users can add an optional alias name to make the drop-down menu easier to identify.

[Bug Fixes]

1. Minor bug fixes and improvements

2021/03/10, version 0.55 #

[Enhancements]

1. Query Form - Save as Query Condition

1.1. Lists only distinct data.

2. Large Text File Splitter

2.1. Supports files larger than 2 GB.

2.2. Displays a progress bar during splitting.

[Bug Fixes]

1. Query Form - SQL to Code

2. Minor bug fixes and improvements

2021/02/17, version 0.54 #

[New Features]

1. Options Form - "Copy Settings..."

1.1. Users can copy all settings from a specified connection name.

[Enhancements]

1. Connection Form - Connection List

1.1. Added a new column: Tab Back Color.

2021/02/04, version 0.53 #

[New Features]

1. Main Form

1.1. Report Bugs: opens reportbugs.html in the default browser.

[Enhancements]

1. Main Form - Release Notes

1.1. Converted the format from text to HTML.

1.2. Opens releasenotes.html in the default browser.

2021/02/01, version 0.52 #

[New Features]

1. Main Form - Right-click menu of TabControl

1.1. Added "New SQL Editor" item

[Enhancements]

1. Export all data to Excel

1.1. Automatically detects whether Excel is in cell editing mode and displays a prompt message if it is.

2. Export all data to CSV - Progress Form

2.1. Disables form resizing.

2.2. Disables the ESC key to prevent the form from being closed. The form can only be closed by using the Cancel button.

3. Updater.exe

3.1. Supports the same multiple languages as JasonQuery.

2021/01/25, version 0.51 #

[New Features]

1. Added one-click update support.

1.1. Click the [Update Now] button from [Help] > [Check for Updates].

1.2. Updater.exe can also be run manually.

2021/01/11, version 0.50 #

[New Features]

1. Query Form

1.1. Support for variables in SQL statements (ex. SELECT * FROM Employee WHERE EmployeeName = :name)

2020/12/30, version 0.49 #

[Enhancements]

1. Query Form

1.1. Export All Data to Excel: saves the exported file path and file name in the drop-down list.

[Bug Fixes]

1. Query Form

1.1. Copy as Query Condition: numeric types do not require single quotes.

2020/12/21, version 0.48 #

[Bug Fixes]

1. Query Form

1.1. PostgreSQL: fixed incorrect error positioning when executing SQL statements.

2. Fixed a bug in "Disconnect Automatically".

2020/12/14, version 0.47 #

[Enhancements]

1. Query Form

1.1. Data Grid: after "Next Page" is triggered, focus always returns to the Data Grid.

2. Options Form

2.1. SQL to Code: added descriptions for Styles 1 to 3.

3. Check for Updates Form

3.1. Added two buttons: "How to Update Manually" and "Open JasonQuery Path".

[Bug Fixes]

1. Check for Updates Form

1.1. Stopped using 1MB.co to detect new versions because it no longer provides free service.

2. Query Form

2.1. Minor bug fixes for "Indent", "Unindent", "Comment", "Uncomment"

2.2. Data Grid: after pressing Ctrl+End, scrolling the mouse wheel could unexpectedly zoom in or out.

2.3. Quick search bar: Find Next / Find Previous could not find "CX" in "CCXX".

2020/12/09, version 0.46 #

[Enhancements]

1. Connection Form

1.1. Replaced the database icons downloaded from icons8.com.

[Bug Fixes]

1. Query Form

1.1. Data Grid quick search bar: fixed the search function.

2020/12/07, version 0.45 #

[Enhancements]

1. Query Form

1.1. Made the Find and Replace panel movable.

[Bug Fixes]

1. SQL History Form

1.1. Minor bug fixes for search function

2020/12/03, version 0.44 #

[Bug Fixes]

1. Query Form

1.1. Paging Query: when Paging Query is disabled, PageDown or Down Arrow no longer triggers Next Page automatically.

2. PostgreSQL

2.1. Fixed the PostgreSQL error: "This PgSqlTransaction has completed; it is no longer usable."

2020/12/01, version 0.43 #

[Bug Fixes]

1. Query Form

1.1. Minor bug fixes for "UPPER Case" and "lower Case".

2020/11/30, version 0.42 #

[New Features]

1. Connection Form

1.1. Enable Pooling: connection pooling allows JasonQuery to reuse connections from a pool instead of reestablishing a connection for each use.

1.2. Once a connection has been created and placed in a pool, JasonQuery can reuse it without performing the full connection process.

[Bug Fixes]

1. Minor bug fixes for "Disconnect automatically"

2020/11/25, version 0.41 #

[New Features]

1. Options Form

1.1. Data Grid: added "Set Focus to Data Grid after Execute Query Statement". It is disabled by default.

[Enhancements]

1. SQL History Form

1.1. Minor bug fixes and improvements

2. Updated the help content for the "Raw Data Mode" button.

2020/11/19, version 0.40 #

[New Features]

1. Added SQL Server support. Schema Browser Form support was not yet complete.

2. Query Form

2.1. Added Paging Query support for Oracle, PostgreSQL, and SQL Server.

2.2. The default page size is 500 rows.

2.3. Users can click Next Page to append the next 500 rows.

2.3.1. Click the Next Page button at the bottom right of the Main Form.

2.3.2. Press PageDown or Down Arrow on the last line.

2.3.3. Scroll to the bottom of the Data Grid.

2.4. Users can temporarily enable or disable Paging Query using the checkbox at the bottom right of the Main Form.

3. Options - Data Grid

3.1. Users can enable or disable Paging Query.

3.2. Users can change the number of rows fetched per page: 100, 500, 1000, 2000, or 5000.

Updated Component:

1. Devart.Data.dll - 5.0.2551.0

2. Devart.Data.Oracle.dll - 9.13.1127.0

3. Devart.Data.PostgreSql.dll - 7.19.1759.0

New Component:

1. Devart.Data.SqlServer.dll - 3.0.397.0

2020/11/09, version 0.39 #

[Enhancements]

1. Query Form

1.1. Improved the Cancel button.

2020/11/03, version 0.38 #

[Enhancements]

1. Query Form

1.1. Code to SQL for C#: when the following keywords are detected at the beginning of a line, the whole line is treated as an empty value.

1.1.1. "if", "else"

2020/10/30, version 0.37 #

[Bug Fixes]

1. Query Form

1.1. Minor bug fixes and improvements

2020/10/29, version 0.36 #

[Enhancements]

1. Query Form

1.1. Increased the allowed file size for opening files to reduce out-of-memory errors.

1.2. JasonQuery x86: recommended file size is less than 50 MB.

1.3. JasonQuery x64: recommended file size is less than 300 MB.

2020/10/12, version 0.35 #

[Enhancements]

1. When executing non-query batch SQL statements, write each statement to SQL History separately to avoid the SQL History query becoming unresponsive when the batch contains too many statements.

2. Updated the help content for the "Raw Data Mode" button.

[Bug Fixes]

1. Export all data to Excel:

1.1. Fixed the worksheet name issue.

1.2. Fixed the cell background color issue.

2020/10/05, version 0.34 #

[New Features]

1. Export all data to Excel

1.1. Users can define and save export settings.

1.1.1. Examples: file name, file type, worksheet name, grid color, and other settings.

[Bug Fixes]

1. Export all data to Excel:

1.1. Numeric data types, such as int and number, are now displayed as numeric values in Excel.

2020/09/29, version 0.33 #

[Enhancements]

1. Options Form

1.1. Data Grid: added the "Raw Data Mode" option, allowing users to decide whether to use this feature.

[Bug Fixes]

1. Query Form

1.1. Commit and Rollback buttons: due to a bug, the execution method was changed from SQL command to function call.

2020/09/28, version 0.32 #

[Enhancements]

1. PostgreSQL: added the following data types.

1.1. boolean, smallint, bigint, real, double precision, int32[], text[]

[Bug Fixes]

1. Query Form

1.1. Commit and Rollback buttons now save "commit;" or "rollback;" to SQL History.

2020/09/26, version 0.31 #

[Enhancements]

1. Connection Form

1.1. Required fields are displayed with a light yellow background.

1.2. Rewrote the connection handling so each data source uses its own independent object.

[Bug Fixes]

1. Query Form

1.1. If a SQL statement contains a variable such as :name and the variable causes an error during execution, JasonQuery positions the error indicator at that variable.

2020/09/17, version 0.30 #

[Enhancements]

1. Query Form

1.1. Commit and Rollback buttons

1.1.1. The execution method was changed from function call to SQL command.

1.1.2. For example, clicking the Commit button directly executes the "commit;" command.

1.1.3. For example, clicking the Rollback button directly executes the "rollback;" command.

1.2. Auto Replace

1.2.1. Automatically adjusts row height according to the user-defined replacement value, up to 3 lines.

2020/09/14, version 0.29 #

[New Features]

1. Query Form

1.1. Save As: added the F12 shortcut.

2. In any window, users can press Ctrl+N to open a new Query Form or Ctrl+O to open an existing file.

[Enhancements]

1. When "commit;" or "rollback;" is executed separately, the "Not yet committed or rolled back!" prompt is hidden.

2. PostgreSQL: if "Enable Auto Rollback" is not enabled, the Rollback button is automatically enabled when a SQL statement execution error occurs.

3. If SQL execution has not finished and the user clicks Commit or Rollback, JasonQuery ignores the action to avoid unnecessary errors.

2020/09/09, version 0.28 #

[New Features]

1. Query Form

1.1. Added "Raw Data Mode"

1.2. Enabling this feature can greatly speed up query result display.

1.3. Click the "?" button to display detailed information.

[Enhancements]

1. Disconnect Automatically: added the "Never" option and changed the default value to "Never".

[Bug Fixes]

1. Query Form

1.1. Data Grid's search function

1.2. PostgreSQL: fixed an issue where the error position indicator could be offset.

2. Connection Form

2.1. Fixed a minor bug in the Copy button.

2020/09/03, version 0.27 #

[New Features]

1. Options Form

1.1. Data Grid: added "Preview CLOB Data". It is disabled by default.

2. Query Form

2.1. Added "Options" button

2.1.1. Users can quickly switch settings such as "Result Copy Quoting With", "Result Copy Field Separator", and "Preview CLOB Data".

[Enhancements]

1. Query Result: when "Preview CLOB Data" is disabled

1.1. Oracle BLOB columns display "(BLOB)".

1.2. Oracle CLOB/NCLOB columns display "(CLOB)".