Skip to content

Bug: MySQL Completion Not Working, but Works for PostgreSQL #85

@itse4elhaam

Description

@itse4elhaam

I'm using vim-dadbod-completion with vim-dadbod and sqls for SQL autocompletion. Everything works as expected when editing a psql file inside a vim-dadbod-ui buffer, but when working in a mysql file, the completion is missing or significantly different.

Additional Information:

  • :checkhealth lspconfig shows that sqls is attached to both buffers (psql and mysql).
  • vim-dadbod is managing the database connections correctly.
  • vim-dadbod-completion is providing completions in psql, but not mysql.
  • sqls is set up to recognize sql, mysql, and plsql filetypes.
  • No errors are shown, and completions simply do not appear.

Debug Output
Here's the relevant output from :checkhealth lspconfig when inside both buffers:

PostgreSQL (psql buffer, working completion)

  • Detected filetype: sql

  • 2 client(s) attached: null-ls, sqls
    MySQL (mysql buffer, broken completion)

  • Detected filetype: mysql

  • 1 client attached: sqls

  • Completion is not working

Questions

Could this be a filetype issue where vim-dadbod-completion isn't recognizing mysql as sql?
Does vim-dadbod-completion handle MySQL completion differently from PostgreSQL?
Any known workarounds or fixes?

Let me know if I can provide any additional debugging info. Thanks for the great plugin!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions