10 Commits (1f11f806413837b2f41046c46b8963b8e0ae6b5f)

Author	SHA1	Message	Date
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?	2 years ago
Francisco Ingham	3f29742adc	Sql alchemy commands used in table info (#1135) ... This approach has several advantages: * it improves the readability of the code * removes incompatibilities between SQL dialects * fixes a bug with `datetime` values in rows and `ast.literal_eval` Huge thanks and credits to @jzluo for finding the weaknesses in the current approach and for the thoughtful discussion on the best way to implement this. --------- Co-authored-by: Francisco Ingham <> Co-authored-by: Jon Luo <20971593+jzluo@users.noreply.github.com>	2 years ago
Harrison Chase	5e10e19bfe	Harrison/align table (#1081) ... Co-authored-by: Francisco Ingham <fpingham@gmail.com>	2 years ago
Harrison Chase	ec727bf166	Align table info (#999) (#1034) ... Currently the chain is getting the column names and types on the one side and the example rows on the other. It is easier for the llm to read the table information if the column name and examples are shown together so that it can easily understand to which columns do the examples refer to. For an instantiation of this, please refer to the changes in the `sqlite.ipynb` notebook. Also changed `eval` for `ast.literal_eval` when interpreting the results from the sample row query since it is a better practice. --------- Co-authored-by: Francisco Ingham <> --------- Co-authored-by: Francisco Ingham <fpingham@gmail.com>	2 years ago
Harrison Chase	f95cedc443	Harrison/sql rows (#915) ... Co-authored-by: Jon Luo <20971593+jzluo@users.noreply.github.com>	2 years ago
Harrison Chase	248c297f1b	Sample row in table info for SQLDatabase (#769) (#782) ... The agents usually benefit from understanding what the data looks like to be able to filter effectively. Sending just one row in the table info allows the agent to understand the data before querying and get better results. --------- Co-authored-by: Francisco Ingham <> --------- Co-authored-by: Francisco Ingham <fpingham@gmail.com>	2 years ago
Amos Ng	fa6826e417	Fix sqlalchemy warnings when running tests (#733) ... This has been bugging me when running my own tests that call langchain methods :P	2 years ago
Andrew Gleave	ea67c049f0	Support SQL statements that return no results (#222) ... Adds support for statements such as insert, update etc which do not return any rows. `engine.execute` is deprecated and so execution has been updated to use `connection.exec_driver_sql` as-per: https://docs.sqlalchemy.org/en/14/core/connections.html#sqlalchemy.engine.Engine.execute	2 years ago
Nicholas Larus-Stone	ca4b10bb74	feat: add option to ignore or restrict to SQL tables (#151) ... `SQLDatabase` now accepts two `init` arguments: 1. `ignore_tables` to pass in a list of tables to not search over 2. `include_tables` to restrict to a list of tables to consider	2 years ago
Harrison Chase	af81e9ca9c	add sql database (#35)	2 years ago