fix(get_view_names): Use proper schema

[philipuvarov]

Hey @Mause ! Thanks for this lib :)

When working with it to wire DuckDB to Superset I have noticed that Superset does not display views created in the DuckDB.

The problem was that get_view_names was using raw table_schema in the WHERE clause, which in case of Superset includes database name, so it becomes something like foodb.barschema. Which means that the WHERE clause in the function to get the view names never succeeds, as it tries to compare table_name to a string that includes database name.

get_table_names uses _build_query_where function that splits database and schema name, so to fix the bug I have used the same approach that _build_query_where function uses to split the schema and db name. We can't really _build_query_where function itself because of how the naming difference(in information_schema.tables schema field is named table_schema and not schema_name as it is named in the duckdb_tables() or duckdb_views()).

I also initially tried using duckdb_views() but that one returns all system views as well, which we don't really need

[conventional-commit-lint-gcf]

🤖 I detect that the PR title and the commit message differ and there's only one commit. To use the PR title for the commit history, you can use Github's automerge feature with squashing, or use automerge label. Good luck human!

-- conventional-commit-lint bot
https://conventionalcommits.org/

[philipuvarov]

@Mause I am not sure I understand CI failures here 🤔 could you take a look?

[philipuvarov]

@Mause bump

[Mause]

Thanks! This has now been released in 0.13.2

Also sorry for the delay 😬

[philipuvarov]

@Mause no worries! Again, thanks a lot for the lib :)