v0.3.0 #99
ajshedivy
announced in
Announcements
v0.3.0
#99
Replies: 1 comment
|
This is a fantastic release! 🎉 The The approach of validating SQL before execution and blocking dangerous operations is crucial for production environments. For teams looking to explore natural language to SQL conversion, tools like ai2sql.io can complement this by helping users construct safe queries before execution. Great work on the enhanced SQL parser for Db2 syntax! 👏 |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
🎯 Overview
Version 0.3.0 introduces the new
execute_sqlbuilt-in tool, enabling AI agents to interact directly with your IBM i database through dynamic SQL queries. This release also includes enhanced SQL parsing, security validation, and architectural improvements.Key Highlights
🚀 What's New
1. New
execute_sqlToolThe headline feature of v0.3.0 is the built-in
execute_sqltool, which allows AI agents to execute arbitrary SQL queries against your IBM i database.Key Capabilities:
Quick Start: Enable the tool and configure security
Read-Only Mode:
When enabled, the tool blocks write operations while allowing queries:
Use Cases:
📚 Reference: #92 - SQL security validation for readonly operations
2. Enhanced SQL Parser
Integrated the SQL parser from the VS Code Db2i extension to improve syntax understanding and validation.
Improvements:
This parser powers the security validation in the new
execute_sqltool, ensuring accurate detection of write operations in read-only mode.📚 Reference: #97 - Add vscode db2i sql parser
🔧 Additional Improvements
Bug Fixes
check_command_audit_settingstool to use modern named parameter syntax (:command_names) instead of deprecated template syntax (#95)Architecture & Performance
📦 Installation & Upgrade
Installation
Run directly
Configuration
Enable the new
execute_sqltool in your.envor MCP client config:Migration Notes:
📚 Resources
What's Changed
New Contributors
Full Changelog: v0.2.0...v0.3.0
This discussion was created from the release v0.3.0.
All reactions