sqlitebrowser / sqlitebrowser/sqlitebrowser
Export triggers with "database to sql" export
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C++
- Stars
- 24.6k
- Forks
- 2.4k
- Avg merge
- 3d 49m
- Merged PRs (30d)
- 3
Description
Describe the new feature
Views are already exported together with your table definitions if scheme only or export everything is selected in the database to sql dialog.
Why not export triggers too?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the database to sql dialog, especially the paths for “scheme only” and “export everything,” and compare how views are handled with triggers. Done means those export modes include the database’s triggers alongside the existing table definitions and views.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, sqlite
- Domain
- database
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100