ENH: Added support for the pd.read_sql to return a dictionary of all tables
- [x] closes #45979 (Replace xxxx with the Github issue number)
- [x] [Tests added and passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#writing-tests) if fixing a bug or adding a new feature
- [x] All [code checks passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit).
- [x] Added an entry in the latest `doc/source/whatsnew/vX.X.X.rst` file if fixing a bug or adding a new feature.

Thanks for the pull request, but we require discussion for enhancement requests before moving forward with pull requests The referenced issue has not been triaged by the core team yet. (As a reference I would be -1 on this enhancement as our other `read_*` methods are not "multi-file/table" aware and trivial to perform in a loop).

Closing for now, but if you'd like to stimulate the discussion in the original issue or work on an enhancement that has been triaged and supported by the core team that would be much appreciated Thanks for the update, I would look at other issues that have been triaged. 

How do I know when an issue has been triaged? Is there a specific label?

Lastly, what does -1 mean on enhancements? I noticed some other figures like -0.5 in some PRs too -1 means almost no chance of the PR being accepted  > How do I know when an issue has been triaged? Is there a specific label?

Any issue with `Needs ...` generally means it has not been fully vetted yet.