langchain/docs/modules/chains/examples
Jon Luo 0a1b1806e9
sql: do not hard code the LIMIT clause in the table_info section (#1563)
Seeing a lot of issues in Discord in which the LLM is not using the
correct LIMIT clause for different SQL dialects. ie, it's using `LIMIT`
for mssql instead of `TOP`, or instead of `ROWNUM` for Oracle, etc.
I think this could be due to us specifying the LIMIT statement in the
example rows portion of `table_info`. So the LLM is seeing the `LIMIT`
statement used in the prompt.
Since we can't specify each dialect's method here, I think it's fine to
just replace the `SELECT... LIMIT 3;` statement with `3 rows from
table_name table:`, and wrap everything in a block comment directly
following the `CREATE` statement. The Rajkumar et al paper wrapped the
example rows and `SELECT` statement in a block comment as well anyway.
Thoughts @fpingham?
2023-03-13 23:08:27 -07:00
..
api.ipynb Harrison/new api chain (#623) 2023-01-15 18:34:43 -08:00
constitutional_chain.ipynb Added constitutional chain. (#1147) 2023-02-18 19:31:51 -08:00
llm_bash.ipynb Custom prompt option for llm_bash and api chains (#612) 2023-01-14 07:22:52 -08:00
llm_checker.ipynb Docs refactor (#480) 2023-01-02 08:24:09 -08:00
llm_math.ipynb add custom prompt for LLMMathChain and SQLDatabase chain (#605) 2023-01-13 06:28:51 -08:00
llm_requests.ipynb Docs refactor (#480) 2023-01-02 08:24:09 -08:00
llm_summarization_checker.ipynb Harrison/summarizer chain (#1356) 2023-03-01 20:59:07 -08:00
moderation.ipynb Docs refactor (#480) 2023-01-02 08:24:09 -08:00
pal.ipynb Add Qdrant named arguments (#1386) 2023-03-02 07:05:14 -08:00
sqlite.ipynb sql: do not hard code the LIMIT clause in the table_info section (#1563) 2023-03-13 23:08:27 -07:00