-
Notifications
You must be signed in to change notification settings - Fork 16.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support (optional) direct return on SQLDatabaseChain
to prevent passing data to LLM
#821
Comments
love this idea, let me get on it |
Merged
thoughts on the above pr? |
Looks great, thanks for the quick response! |
hwchase17
pushed a commit
that referenced
this issue
Feb 3, 2023
zachschillaci27
added a commit
to zachschillaci27/langchain
that referenced
this issue
Mar 8, 2023
mikeknoop
pushed a commit
to zapier/langchain-nla-util
that referenced
this issue
Mar 9, 2023
wertycn
pushed a commit
to wertycn/langchain-zh
that referenced
this issue
Apr 26, 2023
ZinedineDumas
added a commit
to ZinedineDumas/React-Python
that referenced
this issue
Jul 17, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thanks for the amazing open source work!
For certain data-sensitive projects, it may be important to silo the database and its contents (aside from table/column names) from any calls to the LLM. This means the LLM cannot be used for formatting the output of the SQL query. I suppose one way to support this would be to allow something like the
Tool
optionreturn_direct
in theSQLDatabaseChain
chain, but perhaps there's a better way. I'm happy to help contribute as needed.The text was updated successfully, but these errors were encountered: