Toad World® Forums

Use the parameters setup for the object browser when determining what to present users in the code completion so users can use the feature but not with all objects?

For Toad Data Point - use the parameters setup for the object browser when determining what to present users in the code completion

so users can use the feature but not with all objects?

Few extra details.

We are having issues with the catalog query for functions that is triggered by the code completion auto pop-up. Ideally, we’d be able to limit what pop-ups to columns, tables, etcetera. This should prevent visibility in the pop-up as well as execution of the query to gather the unselected objects. The idea was to link it to the selected explorer objects but a separate set of options would be acceptable as well. So, if for Oracle users deselect visibility on functions they wouldn’t show or be collected for auto popup either.

SELECT a.object_name, a.object_type,
DECODE (a.status, 'VALID', 'true', 'false') as valid,
a.last_ddl_time,
a.object_id,
a.created,
case nvl (b.debuginfo, 'F')
when 'F' then 'false'
when 'T' then 'true'
else 'false'
end as debuginfo,
case
when c.owner is not null
then nvl (c.authid, 'CURRENT_USER')
else null
end as authid,
a.status
from all_objects a
left outer join sys.all_probe_objects b on (a.object_id = b.object_id)
left outer join all_procedures c
on (c.owner = a.owner and c.object_name = a.object_name)
WHERE a.owner = :f1 AND a.object_type = 'FUNCTION'
ORDER BY 2, 1 ;