Skip to content

Fully qualified completion #1433

@tlhackque

Description

@tlhackque

Describe the new feature

I may be overly paranoid, but I write SQL with fully-qualified names. That is, with all
database fields qualified by table name and both the table name and field in double quotes.

This is future-proofing - it guarantees that new SQL keywords and table fields won't require
code changes. Whether it's clearer or simply verbose is a matter of preference.

Completion in the editor should support this style. Currently, it's awkward - accept a
field name, then go back and add the double quotes, and the "table" dot before each one.

What I'd like is an editor preference that would cause autocompletion to:

  • If the field name is unique in the schema, automatically prefix the correct table name
  • If the field name is not unique, show it with each possible table name so I can click on the intended one
  • In any case, the completion should include the table name and double-quote both.

E.g., "tablea"."key" "tableb"."key"

For people who work with databases maintained by people with different opinions, it would be ideal if the preference was remembered per-database - but that's not essential.

Additional info

Please answer these questions before submitting your feature request.

Is your feature request related to an issue? Please include the issue number.

No - unless you consider usability an issue.

Does this feature exist in another product or project? Please provide a link.

Don't know.

Do you have a screenshot? Please add screenshots to help explain your idea.

No.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions