Skip to content
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

Unknown dialect 'mssql'. Did you mean mysql? #581

Closed
ontirius opened this issue Aug 5, 2024 · 2 comments · Fixed by Canner/wren-engine#734
Closed

Unknown dialect 'mssql'. Did you mean mysql? #581

ontirius opened this issue Aug 5, 2024 · 2 comments · Fixed by Canner/wren-engine#734
Labels
bug Something isn't working

Comments

@ontirius
Copy link

ontirius commented Aug 5, 2024

Describe the bug
WrenAI response is always: "No relevant SQL found for the given query"
Also with simple questions like: "Lists all row that you find inside table " the strange things is that inside logs of enging I'm able to find a correct query! So seems that the AI works fine, but inside ibis-server logs there is that error: "Unknown dialect 'mssql'. Did you mean mysql?"

To Reproduce
Configure WrenAI to works with MS SQL and fireworks.ai as LLM, and make a question

Expected behavior
We expect a clear response that contains data from MS SQL

Screenshots
image

Desktop (please complete the following information):

  • OS: Win10
  • Browser chrome

Wren AI Information

  • Version: latest
  • LLM_PROVIDER= openai_llm
  • GENERATION_MODEL= accounts/fireworks/models/llama-v3p1-405b-instruct

Many thanks!

@ontirius ontirius added the bug Something isn't working label Aug 5, 2024
@cyyeh
Copy link
Member

cyyeh commented Aug 5, 2024

Issue confirmed, and we will fix it asap. Thank you! cc @grieve54706

@grieve54706
Copy link
Contributor

@wwwy3y3, please close this fixed issue.

@wwwy3y3 wwwy3y3 closed this as completed Oct 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants