Move feat from %sqlrender to %sqlcmd snippets

[bbeat2782]

Describe your changes

Moved %sqlrender feature to %sqlcmd snippets, added FutureWarning when user call %sqlrender, modified API Reference documentation, and modified test functions to test %sqlcmd snippets {snippet_name}

Issue number

Closes #647

Checklist before requesting a review

• Performed a self-review of my code
• Formatted my code with pkgmt format
• Added tests (when necessary).
• Added docstring documentation and update the changelog (when needed)

---

📚 Documentation preview 📚: https://jupysql--656.org.readthedocs.build/en/656/

[yafimvo]

@bbeat2782
lgtm. Please rebase.

@edublancas do you think we should remove the sqlrender guide from the doc tree?

[neelasha23]

This is currently displaying

WITH
SELECT * FROM penguins.csv where species == 'Gentoo'

Is it supposed to display WITH even when it is not used as subquery as part of another query?

Also, previously we could sqlrender the final query as well, that uses a snippet as subquery. e.g.
SELECT * from gentoo where bill_length < 50... can you add a similar example ?

[bbeat2782]

Also, previously we could sqlrender the final query as well, that uses a snippet as subquery. e.g.
SELECT * from gentoo where bill_length < 50... can you add a similar example ?

For this one, when you mentioned sqlrender showing the final query, are you referring to something like the following?

[edublancas]

@neelasha23: yes, this is a bug we discovered recently. I reported it on #657, @bbeat2782 will work on it.

@bbeat2782: please work on this first, and then tackle the other one

[neelasha23]

Added some comments. Few other observations:

1. There are places in the docs where we use sqlrender,e.g., cte. I think we should replace those as well.
2. Please resolve merge conflicts

[bbeat2782]

1. There are places in the docs where we use sqlrender,e.g., cte. I think we should replace those as well.

I was thinking about replacing %sqlrender with %sqlcmd snippets with a separate PR, but if you think it works better with one PR, I will add those changes to this PR.

[edublancas]

I was thinking about replacing %sqlrender with %sqlcmd snippets with a separate PR, but if you think it works better with one PR, I will add those changes to this PR.

yes, please tackle documentation changes here. usually whenever we modify a feature, the PR that changes the feature also updates the docs.

[edublancas]

please address the observations from @neelasha23

[edublancas]

@bbeat2782: we just merged #654 which moved the implementation of %sqlcmd to separate files (same logic, just re-organized in different files). this is causing merge conflicts. check if you can fix them. otherwise it might be better to branch from master and apply your changes manually to the new files

[bbeat2782]

@edublancas it says src/sql/sqlcmd.py is the conflicting file but the Resolve conflicts button is disabled from my side with a message saying "Only those with write access to this repository can merge pull requests."

So it seems like I would have to apply the changes I made manually.

[edublancas]

@edublancas it says src/sql/sqlcmd.py is the conflicting file but the Resolve conflicts button is disabled from my side with a message saying "Only those with write access to this repository can merge pull requests."

I think you'll be able to do it from the CLI, but yeah feel free to do it manually (create a new branch from master and then apply your changes)