datatug / datatug/datatug-core
Proposal: man command
- Dominant language
- Go
- Stars
- 4
- Forks
- 0
- Avg merge
- 1h 46m
- Merged PRs (30d)
- 37
Description
Display object information in terminal
Examples of usage:
- `datatug man dbo.Users@AdventureWorks@DEV` - e.g. show Users table info in "dbo" schema of AdventureWorks database in DEV environment.
- `datatug man dbo.Users@AdventureWorks@localhost:1433` - e.g. show Users table info in "dbo" schema of AdventureWorks database in at `localhost:1433` server.
Consider reverse path as: `env/server ` => `schema` => `object`. Could be good for code completion. E.g.:
- `datatug man DEV.AdventureWorks.dbo.Users` - e.g. show Users table info in "dbo" schema of AdventureWorks database in DEV environment.
- `datatug man localhost:1433.AdventureWorks.dbo.Users` - e.g. show Users table info in "dbo" schema of AdventureWorks database in at `localhost:1433` server.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the existing CLI entry points and how database objects are addressed; this issue does not name specific files or tests. Compare the proposed `datatug man` paths, decide which notation to support, and define completion criteria for displaying object information in the terminal.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100