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
..
integration_tests	cleanup: unify 3 different pdf loaders, rename PagedPDFSplitter (#1615)	2023-03-13 23:06:50 -07:00
unit_tests	sql: do not hard code the LIMIT clause in the table_info section (#1563)	2023-03-13 23:08:27 -07:00
__init__.py	initial commit	2022-10-24 14:51:15 -07:00