Zeeland

@hwchase17 Actually, `schema_sql_db` and the other three are only used by the [SQLDatabaseToolkit](https://github.com/hwchase17/langchain/blob/master/langchain/agents/agent_toolkits/sql/toolkit.py#L18). It is used together. In addition, the other three tools all have mutual references. Eg `InfoSQLDatabaseTool` [description](https://github.com/hwchase17/langchain/blob/master/langchain/tools/sql_database/tool.py#LL65C1-L65C1)...

I think it's a good solution right now. It can well improve the operation effect of agent, the previous operation effect is not so good. Perhaps we should try to...

> Thanks for your suggestion! Passing parameter is a better solution. What do you think about new commit?

I don't know how to solve this [github action problem](https://github.com/hwchase17/langchain/actions/runs/5113051731/jobs/9191813826?pr=5339). Can you give me some suggestion?

@hwchase17 plz review

[duckduckgo_search readme attention](https://github.com/deedy5/duckduckgo_search): Versions before v2.9.4 no longer work as of May 12, 2023

@vowelparrot I wonder why `duckduckgo_search` has release `v3.2.0` but checks failed and said `Because langchain depends on duckduckgo-search (^3.2.0) which doesn't match any versions, version solving failed.`

@vowelparrot I got the following problem. Do you have ideas to solve the problem? ``` And because weaviate-client (3.19.0) depends on requests (>=2.28.0,=2.28.0,=3.15.5,=2.28.0,=2.31.0) and no versions of duckduckgo-search match >3.2.0,=3.15.5,=3.2.0,=3.15.5,

Oh I see. It's a very common problem.

ok I fix it later. Previously, due to dependency version conflicts, I was unable to pass the test.