aboutsummaryrefslogtreecommitdiffstats
path: root/atuin-server/migrations (follow)
Commit message (Collapse)AuthorAge
* refactor server to allow pluggable db and tracing (#1036)Conrad Ludgate2023-06-12
| | | | | | | | | * refactor server to allow pluggable db and tracing * clean up * fix descriptions * remove dependencies
* Restructure account commands to account subcommand (#984)Ellie Huxtable2023-05-17
| | | | | | | | | | | | | | | | | | | * 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
* Add history deletion (#791)Ellie Huxtable2023-03-20
| | | | | | | | | | | | | * Drop events. I'd still like to do them, but differently * Start adding delete api stuff * Set mailmap * Delete delete delete * Fix tests * Make clippy happy
* Add local event log storage (#390)Ellie Huxtable2022-11-04
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Add event data structures This adds the data structures required to start syncing events, rather than syncing history directly. Adjust event Fix Add event data structure to client * Add server event table sql * Add client event table migration Adjust migration * Insert into event table from client * Add event merge function Right now this just ensures we have the right amount of events given the history we have BUT it will also be used to merge CREATE/DELETE events, resulting in history being deleted :) * Make CI happy * Adjust * we don't limit history length any more * Update atuin-client/src/database.rs Co-authored-by: Conrad Ludgate <conradludgate@gmail.com> * fix usage * Fix typo * New Rust, new clippy stuff Co-authored-by: Conrad Ludgate <conradludgate@gmail.com>
* Add configurable history length (#447)Ellie Huxtable2022-06-10
| | | | | | | | | | | | | * Add configurable history length This allows servers to decide the max length of each history item they want to store! Some users might have much larger history lines than others. This setting can be set to 0 to allow for unlimited history length. This is not recommended for a public server install, but for a private one it can work nicely. * Format lol
* Add created_at column to users (#354)Ellie Huxtable2022-04-26
|
* SQLx cannot run this migration OK (#353)Ellie Huxtable2022-04-26
| | | And also correct a typo
* Add btree index on history table (#345)Ellie Huxtable2022-04-26
| | | This speeds up a whole bunch of our queries by a *lot* :)
* Allow for larger commands (#321)Ellie Huxtable2022-04-21
| | | Followup: Limit command length client side too
* Fix delete trigger (#317)Ellie Huxtable2022-04-21
| | | | I've tested this again by deleting my full history and re-syncing, all good.
* Add count trigger (#308)Ellie Huxtable2022-04-19
| | | | | This can be used in a later PR to optimise our database usage significantly. Avoiding COUNT will be fantastic for our CPU usage, and therefore sync times.
* Update docs, unify on SQLx, bugfixes (#40)Ellie Huxtable2021-04-25
* Begin moving to sqlx for local too * Stupid scanners should just have a nice cup of tea Random internet shit searching for /.env or whatever * Remove diesel and rusqlite fully