Add SQL safety validation and query intent classification to Text-to-SQL pipeline#1
Open
kriti20041 wants to merge 2 commits intoSaba-Gul:mainfrom
Open
Add SQL safety validation and query intent classification to Text-to-SQL pipeline#1kriti20041 wants to merge 2 commits intoSaba-Gul:mainfrom
kriti20041 wants to merge 2 commits intoSaba-Gul:mainfrom
Conversation
Updated project description and usage instructions in README.md.
Refactor OpenAI API key handling and improve SQL safety checks. Update Gradio UI for better user experience.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR enhances the Text-to-SQL analytics pipeline by adding safety and interpretability layers on top of LLM-generated SQL queries.
Changes
Motivation
LLM-generated SQL can be unsafe and difficult to interpret in production environments.
These changes introduce guardrails and reasoning layers to ensure secure, read-only execution and better understanding of user analytics intent.
Impact
Testing