Amazon Redshift implemented cross-database joins all the way back in 2020. It appears that this functionality cannot be utilized within DBVisualizer, as DBVis is always attempting to query either the selected catalog or the default database that is passed as part of the connection string.
Am I missing something? Is there a workaround or plan to properly implement this?
SELECT
loc.*,
ll.*
FROM
[staging].coredata.location loc
LEFT JOIN
[production].user_defined.location_lookup ll
ON
(
ll.organizationid = loc.organizationid
AND loc.id = ll.id);
[Code: 0, SQL State: XX000] ERROR: Could not find parent table for alias "production.user_defined.location_lookup".
1 person has this question
1 Comment
D
Dmitry Palagin
said
8 months ago
Hi Reid,
Just adding a note here that this was due to a vendor issue outside of DbVisualizer, as we discussed in the support channel.
Reid Holland
Amazon Redshift implemented cross-database joins all the way back in 2020. It appears that this functionality cannot be utilized within DBVisualizer, as DBVis is always attempting to query either the selected catalog or the default database that is passed as part of the connection string.
Am I missing something? Is there a workaround or plan to properly implement this?
SELECT
loc.*,
ll.*
FROM
[staging].coredata.location loc
LEFT JOIN
[production].user_defined.location_lookup ll
ON
(
ll.organizationid = loc.organizationid
AND loc.id = ll.id);
[Code: 0, SQL State: XX000] ERROR: Could not find parent table for alias "production.user_defined.location_lookup".
1 person has this question