Skip to content

Feature Request: Support sdev_link_* navigation in query results grid #22

@daemon4-sergio

Description

@daemon4-sergio

Feature Request

Summary

SQL Developer Desktop supports a convention where query result columns prefixed with sdev_link_* (sdev_link_owner, sdev_link_name, sdev_link_type, sdev_link_line) are consumed internally to make result rows navigable. When the user double-clicks any cell in a result row, SQL Developer opens the corresponding database object and positions the cursor at the specified line.

The VS Code extension does not implement this behaviour — those columns appear as regular text in the results grid.

Why this matters

The extension itself includes a built-in Report to search source code (ALL_SOURCE) that already generates a query using the sdev_link_* convention correctly. However, since the extension does not interpret those columns, the navigation capability is completely lost — the user gets the data but cannot navigate to the object.

This creates an ironic situation: the extension generates the right query but cannot use it, while SQL Developer Desktop can use it but does not generate it.

Expected behaviour

When a query result contains sdev_link_owner, sdev_link_name, sdev_link_type, and/or sdev_link_line columns:

  • Those columns should be hidden from the visible results grid
    • Double-clicking (or a similar interaction) on any row should open the corresponding database object in the extension's object viewer, positioned at the indicated line

Example query (already used in the built-in Report)

SELECT owner           "Owner",
       name            "PL/SQL Object Name",
       type            "Type",
       line            "Line",
       text            "Text",
       owner           sdev_link_owner,
       name            sdev_link_name,
       type            sdev_link_type,
       line            sdev_link_line
FROM   sys.all_source
WHERE  owner = USER
ORDER  BY owner, name, type, line;

Environment

  • Oracle SQL Developer Extension for VS Code
    • SQL Developer Desktop 24.3.1.347 (for reference — this is where the behaviour works correctly)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions