SQL Completion

The query pad provides SQL completion for table names, column names, aliases, SQL keywords, and federation schema prefixes. Completion fires automatically as you type or on demand with <C-Space>.

Built-in completion

Enabled by default. The built-in completion uses Neovim’s omnifunc mechanism (<C-x><C-o>) and registers itself on the query pad buffer. No configuration needed.

Using blink.cmp

If you use blink.cmp for completion across Neovim, disable the built-in completion and register the dadbod_grip source:

require('dadbod-grip').setup({
  completion = false,
})

Then add dadbod_grip to your blink.cmp sources:

require('blink.cmp').setup({
  sources = {
    default = { 'lsp', 'path', 'buffer', 'dadbod_grip' },
  },
})

The dadbod_grip source name is registered automatically when the plugin loads. You only need to add it to your blink.cmp sources list.

Using nvim-cmp

Same pattern: disable built-in, add the source.

require('dadbod-grip').setup({
  completion = false,
})

Then register the source in nvim-cmp:

local cmp = require('cmp')
cmp.setup({
  sources = cmp.config.sources({
    { name = 'nvim_lsp' },
    { name = 'dadbod_grip' },
  }),
})

What gets completed

In a DuckDB federation session, completion includes qualified names from all attached databases. Type prod. to see tables from the prod attachment, or prod.customers. to see columns.

Manual trigger

Press <C-Space> in the query pad to manually trigger completion at any time. Press <C-x><C-o> for the standard Vim omnifunc trigger if you prefer. While the completion menu is open, Tab and <Down> move forward, <S-Tab> and <Up> move backward, and <CR> accepts the selected item. Setting completion = false removes these completion-specific mappings from the query pad.