-
Notifications
You must be signed in to change notification settings - Fork 839
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
something wrong with question_sql_list
#451
Comments
This is intentional -- the question-SQL pairs as user/assistant messages is in-context learning and how the LLM will know to follow the pattern and generate SQL correctly. You can dial down the number of those that are used by setting the
|
Ok, I thought you wanted to use |
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
vanna version: 0.5.5
something wrong with
question_sql_list
, I suspect there might be an issue with the usage of question_sql_list. Every time a search is conducted, question_sql_list is added to the historical conversation, which unnecessarily consumes my GPT tokens. Could you please check this?For example, when I asked a few questions, the resulting historical conversation is as follows:
However, I am just using
vn_rtn = vn.ask(question="Are there any branches in Shanghai?", visualize=False).
.This is just a single-turn conversation, so why is it being constructed as a historical conversation?
To Reproduce
My complete code is as follows, I just change the
question
each time, you can run the code to reproduce the result:Expected behavior
a single-turn conversation.
The text was updated successfully, but these errors were encountered: