langchain

Commit Graph

Author	SHA1	Message	Date
Jon Luo	92ab27e4b8	sql doc formatting (#1350 ) My bad, missed a few tabs between the two PRs	1 year ago
Jon Luo	35f1e8f569	separate columns by tabs instead of single space in sql sample rows (#1348 ) Use tabs to separate columns instead of a single space - confusing when there are spaces in a cell	1 year ago
Jon Luo	5bf8772f26	add option to use user-defined SQL table info (#1347 ) Currently, table information is gathered through SQLAlchemy as complete table DDL and a user-selected number of sample rows from each table. This PR adds the option to use user-defined table information instead of automatically collecting it. This will use the provided table information and fall back to the automatic gathering for tables that the user didn't provide information for. Off the top of my head, there are a few cases where this can be quite useful: - The first n rows of a table are uninformative, or very similar to one another. In this case, hand-crafting example rows for a table such that they provide the good, diverse information can be very helpful. Another approach we can think about later is getting a random sample of n rows instead of the first n rows, but there are some performance considerations that need to be taken there. Even so, hand-crafting the sample rows is useful and can guarantee the model sees informative data. - The user doesn't want every column to be available to the model. This is not an elegant way to fulfill this specific need since the user would have to provide the table definition instead of a simple list of columns to include or ignore, but it does work for this purpose. - For the developers, this makes it a lot easier to compare/benchmark the performance of different prompting structures for providing table information in the prompt. These are cases I've run into myself (particularly cases 1 and 3) and I've found these changes useful. Personally, I keep custom table info for a few tables in a yaml file for versioning and easy loading. Definitely open to other opinions/approaches though!	1 year ago
Harrison Chase	45b5640fe5	fix sql (#1141 )	1 year ago
Harrison Chase	5e10e19bfe	Harrison/align table (#1081 ) Co-authored-by: Francisco Ingham <fpingham@gmail.com>	1 year 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>	1 year ago
Harrison Chase	f95cedc443	Harrison/sql rows (#915 ) Co-authored-by: Jon Luo <20971593+jzluo@users.noreply.github.com>	1 year ago
Zach Schillaci	4c79100b15	Correct prompt typo + update example for SQLDatabaseChain (#868 ) See https://github.com/hwchase17/langchain/issues/821	1 year ago
Harrison Chase	94ae126747	return sql intermediate steps (#792 )	1 year 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>	1 year ago
Harrison Chase	6be5f4e4c4	Harrison/sql db chain (#641 ) Co-authored-by: Bruno Bornsztein <bruno.bornsztein@gmail.com>	1 year ago
Harrison Chase	3d43906572	Harrison/new api chain (#623 ) Co-authored-by: Francisco Ingham <fpingham@gmail.com> Co-authored-by: lesscomfortable <pancho_ingham@hotmail.com>	1 year ago
Harrison Chase	1c71fadfdc	more complex sql chain (#619 ) add a more complex sql chain that first subsets the necessary tables	1 year ago
Harrison Chase	9f9afbb6a8	add custom prompt for LLMMathChain and SQLDatabase chain (#605 )	1 year ago
Harrison Chase	985496f4be	Docs refactor (#480 ) Big docs refactor! Motivation is to make it easier for people to find resources they are looking for. To accomplish this, there are now three main sections: - Getting Started: steps for getting started, walking through most core functionality - Modules: these are different modules of functionality that langchain provides. Each part here has a "getting started", "how to", "key concepts" and "reference" section (except in a few select cases where it didnt easily fit). - Use Cases: this is to separate use cases (like summarization, question answering, evaluation, etc) from the modules, and provide a different entry point to the code base. There is also a full reference section, as well as extra resources (glossary, gallery, etc) Co-authored-by: Shreya Rajpal <ShreyaR@users.noreply.github.com>	1 year ago

15 Commits (97bcca751833aa8d2bb4bb885ef274a42676f991)