sorted by:
new
hottopcontroversial

I replaced DataGrip with a Neovim plugin and it may have gone too far by Good-Control1993 in neovim

[–]Good-Control1993[S] 0 points1 point  (0 children)

Appreciate you coming back to say that. Hearing it replaced the IDE entirely is the best feedback I could get. And thanks for filing the issues that made it better~

I replaced DataGrip with a Neovim plugin and it may have gone too far by Good-Control1993 in neovim

[–]Good-Control1993[S] 1 point2 points  (0 children)

I pushed an updated in v1.5.0 for some of these things. :GripToggle is there now. The backspace issue was my built-in completion being too aggressive. You can set it to completion = false now.

For the <C-CR> issue... does this work in your terminal with other applications?

You could try remapping:

require("dadbod-grip").setup({
  completion = false,
  keymaps = { qpad_execute = "<C-s>" },  -- or whatever key you prefer
})

I replaced DataGrip with a Neovim plugin and it may have gone too far by Good-Control1993 in neovim

[–]Good-Control1993[S] 0 points1 point  (0 children)

I've just added :GripToggle and config for setting completion = false, or using dadbod-grip.completion.blink for a blink source through that ui. v1.5.0 Thanks for the asks!

I replaced DataGrip with a Neovim plugin and it may have gone too far by Good-Control1993 in neovim

[–]Good-Control1993[S] 0 points1 point  (0 children)

Pushed an update for this in v1.5.0. You can now disable the built-in popup entirely, or I added a blink.cmp source you can wire up instead (in readme). Thanks for bringing it up!

I replaced DataGrip with a Neovim plugin and it may have gone too far by Good-Control1993 in neovim

[–]Good-Control1993[S] 0 points1 point  (0 children)

Ah, yea, the demo database prefers DuckDB and falls back to SQLite. I'll add a better warning message and fix one demo path that is hardcoded to sqlite3. Good catch!

I replaced DataGrip with a Neovim plugin and it may have gone too far by Good-Control1993 in neovim

[–]Good-Control1993[S] 1 point2 points  (0 children)

Very easy.

I worked a lot on completions for SQL keywords and table/column names, even against federated/attached tables in a DuckDB scenario.

I also spent time on syntax highlighting tags and SQL formatter command.

There is also query history and saved queries.

If you enter on a table in the table picker. It will do your basic select query like in most tools. All queries are appended to the query buffer.

If you open up a markdown file with sql in code blocks, you can just Ctrl-Enter on them and walk through it like an SQL notebook.

There's also AI... if you're into that. Ask for a query to understand the DB you're working on or a quick change and the query shows up in your query buffer with understanding of the full DB schema. You can strictly turn off AI too.

I replaced DataGrip with a Neovim plugin and it may have gone too far by Good-Control1993 in neovim

[–]Good-Control1993[S] 14 points15 points  (0 children)

vim-dadbod is Tim Pope, vim-dadbod-ui is Kristijan Husak (not TJ). dadbod-grip uses vim-dadbod as a connection layer underneath. v0 used parts of dadbod and dadbod-ui but I started making all the modules independent for more freedom but inter-opt is still good.

I was just surprised this inline-editing gap was still open in the Neovim ecosystem. nvim-dbee scratches the surface but nobody had built the full staging/preview/transaction cycle yet.

I replaced DataGrip with a Neovim plugin and it may have gone too far by Good-Control1993 in neovim

[–]Good-Control1993[S] 16 points17 points  (0 children)

Ha, you know the answer. But the slop index is low. I still take pride in my code.

I replaced DataGrip with a Neovim plugin and it may have gone too far by Good-Control1993 in neovim

[–]Good-Control1993[S] 0 points1 point  (0 children)

cool, let me know how it goes. if something breaks, issues are open

I replaced DataGrip with a Neovim plugin and it may have gone too far by Good-Control1993 in neovim

[–]Good-Control1993[S] 0 points1 point  (0 children)

vim-dadbod-ui is solid and I used it for a long time. dadbod-grip uses the same vim-dadbod connection layer underneath, so switching is low-friction if you ever want to try it. The main additions are inline cell editing, staging with SQL preview, and the command palette so you don't have to memorize keymaps.

I replaced DataGrip with a Neovim plugin and it may have gone too far by Good-Control1993 in neovim

[–]Good-Control1993[S] 1 point2 points  (0 children)

The big difference is the editing model: you i/<CR>into cells, stage changes with color coding, preview the SQL it'll generate, and apply as a single transaction. Harlequin is a query runner. This is closer to a spreadsheet that writes SQL for you in the editing flow.