-
-
Notifications
You must be signed in to change notification settings - Fork 507
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Restructure account commands to account subcommand #984
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While this works as it did before, I realise that we don't count actual history delete requests here. Should we add a trigger on update? I think users might be confused if the remote count doesn't decrease when they delete
I wish :( If we actually update the remote count when rows are soft deleted, sync won't work. It's append-only, afterall, and expects counts to always increase |
We should perhaps offset the deleted items from the remote count before displaying it though |
* Stop running triggers on history delete * Move to account management dir * Alter trigger function to only run for inserts * wip * Add atuin account subcommands, and re-org delete * Clarify docs * Delete silly dupe migration * Um where did this come from * Oops, insert only plz
Also edit the history count trigger so it only runs on insert, and not on delete. This will make sure that deletes run super fast 🚀