feature: adapter parity

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

noe.trevino/dadbod-ui.nvim#95

noe.trevino commented

2026-07-15 17:48:59 -05:00

Owner

Did you check the docs?

I have read all the dadbod-ui.nvim docs

Some features only work on some adapters. If youre a sql server user, EXPLAIN just isnt there, and nothing tells you why. Thats a bad first impression for a release.

I dont want to ship something where half the features quietly dont apply to you depending on which database you opened.

Describe the solution you'd like

Every feature that at least one adapter has today should work on postgres, sql server, sqlite, mysql and mariadb, wherever the engine and its cli allow it.

Parity, not completeness. A feature no adapter has yet is a roadmap item and not a gap, so table DDL (#90) is not in scope here. Cells marked ❌ in the matrix are already satisfied, theres nothing to build.

Those five span the abstraction rather than being the popular ones. Postgres has schemas and routines and LIMIT/OFFSET, sql server has schemas and routines but no LIMIT at all, sqlite has neither schemas nor routines, mysql and mariadb add the third pagination style. If a feature works across those five the adapter api is probably right.

Oracle, clickhouse, bigquery and mongo stay the goal, just not a blocker for this milestone.

Acceptance Criteria

Script As - routines
- MySQL
- MariaDB
EXPLAIN
- SQL Server
EXPLAIN ANALYZE
- SQL Server
- SQLite
Auto-pagination
- SQL Server
Vertical layout
- SQL Server
- SQLite
Native CLI export
- SQL Server
CURRENT_SUPPORT.md matrix updated as each one lands

Only auto-pagination is real work. Sql server needs OFFSET/FETCH which is a third pagination style, and it needs an ORDER BY that might not be in the users query. The rest are one template or one flag each.

Describe alternatives/other solutions you've considered

One issue per cell. Thats 9 issues tracking state the feature matrix already tracks, and every fix would mean closing an issue and flipping a cell. The matrix is the tracker, this is just the todo list until prerelease.

Including oracle, clickhouse, bigquery and mongo. Much more surface for a first release, and the four of them are the specialised ones. They stay in CURRENT_SUPPORT.md as the goal.

### Did you check the docs? - [X] I have read all the dadbod-ui.nvim docs ### Is your feature request related to a problem? Please describe. Some features only work on some adapters. If youre a sql server user, EXPLAIN just isnt there, and nothing tells you why. Thats a bad first impression for a release. I dont want to ship something where half the features quietly dont apply to you depending on which database you opened. ### Describe the solution you'd like Every feature that at least one adapter has today should work on postgres, sql server, sqlite, mysql and mariadb, wherever the engine and its cli allow it. Parity, not completeness. A feature no adapter has yet is a roadmap item and not a gap, so table DDL (#90) is not in scope here. Cells marked ❌ in the matrix are already satisfied, theres nothing to build. Those five span the abstraction rather than being the popular ones. Postgres has schemas and routines and LIMIT/OFFSET, sql server has schemas and routines but no LIMIT at all, sqlite has neither schemas nor routines, mysql and mariadb add the third pagination style. If a feature works across those five the adapter api is probably right. Oracle, clickhouse, bigquery and mongo stay the goal, just not a blocker for this milestone. ### Acceptance Criteria - [ ] Script As - routines - [ ] MySQL - [ ] MariaDB - [ ] EXPLAIN - [ ] SQL Server - [ ] EXPLAIN ANALYZE - [ ] SQL Server - [ ] SQLite - [ ] Auto-pagination - [ ] SQL Server - [ ] Vertical layout - [ ] SQL Server - [ ] SQLite - [ ] Native CLI export - [ ] SQL Server - [ ] `CURRENT_SUPPORT.md` matrix updated as each one lands Only auto-pagination is real work. Sql server needs OFFSET/FETCH which is a third pagination style, and it needs an ORDER BY that might not be in the users query. The rest are one template or one flag each. ### Describe alternatives/other solutions you've considered One issue per cell. Thats 9 issues tracking state the feature matrix already tracks, and every fix would mean closing an issue and flipping a cell. The matrix is the tracker, this is just the todo list until prerelease. Including oracle, clickhouse, bigquery and mongo. Much more surface for a first release, and the four of them are the specialised ones. They stay in `CURRENT_SUPPORT.md` as the goal.

Rows
Columns

feature: adapter parity #95

Did you check the docs?

Is your feature request related to a problem? Please describe.

Describe the solution you'd like

Acceptance Criteria

Describe alternatives/other solutions you've considered