Word of caution for those using Toad Data Point for Vertica: SEARCH_PATH does not work properly
Awhile back I'd reported a bug in how Toad Data Point handles Vertica's SEARCH_PATH.
In a nutshell, until the bug is resolved, users should be aware that Toad Data Point will override user's SEARCH_PATH with the single schema in the dropdown. Literally every SQL command is preceded by this SEARCH_PATH override, so if my dropdown-schema is SCHEMA_FOO, running these two commands consecutively:
SET SEARCH_PATH SCHEMA_BAR;
will return SEARCH_PATH of:
'SCHEMA_FOO, v_catalog, v_monitor, v_internal'
This is tangentially related to my previously-reported bug on UDAF schema in views. Combined, the TOAD Data Point SEARCH_PATH-override bug and the UDAF-schema bug prevent me from joining any two views which have UDAF from separate schemas (I can only point TOAD to one schema, and whichever I choose, the view with UDAF from the other schema will give error).