Tried this and you’re right, when you select/de-select a column it removes the schema.
However, it does not seem to recognize the new schema or updated tables (e.g. legacy tables had ‘_cd’ suffix on keys and new tables have ‘_code’).
When do the above the schema disappears from the query but the tables do not update to reflect the new schema/table naming.
Then any time I try to run the query (whether I correct the column names in the Query tab or not) I get an error that the table does not exist (see below).
[Amazon][Amazon Redshift] (30) Error occurred while trying to execute a query: [SQLState 42P01] ERROR: relation “table_name” does not exist.
What we really need is a way to point QB to new schemas within a connection. If you right-click the QB name you can change the DB connection but there doesn’t seem to be a way to point to new schema within a connection and then have the tables refreshed for column name changes.
Is there a feature-request area on this site where I can log this (or vote for it as I’m sure this is not the first time this has been an issue for a user)?