Queries crate #16
Conversation
| @@ -0,0 +1,18 @@ | |||
| use diesel::SelectableHelper; | |||
There was a problem hiding this comment.
crud.rs -> operations.rs? query_repository.rs? Something else?
| debug = false | ||
|
|
||
| [workspace.dependencies] | ||
| queries = { path = "crates/queries" } |
| 'running', | ||
| 'successful', | ||
| 'failed', | ||
| 'canceled', |
| queued_at TIMESTAMP WITH TIME ZONE, | ||
| running_at TIMESTAMP WITH TIME ZONE, | ||
| successful_at TIMESTAMP WITH TIME ZONE, | ||
| failed_at TIMESTAMP WITH TIME ZONE, |
There was a problem hiding this comment.
Maybe just single timestamp, status should describe the state, like failed, cancelled, etc.
There was a problem hiding this comment.
Maybe those final (cancelled, timed out, failed, successful) states could reuse the same timestamp like finished_at, but other intermediate separate timestamps give information on how many time query spends on every stage.
There was a problem hiding this comment.
what does limit_exceeded_at mean?
and what it the difference between queued_at and created_at?
Is running_at means that we can have some queries queue and run it when the server is ready?
There was a problem hiding this comment.
concurrent limit exceeded is actually a state. queued is reserved and it is probably one of intermediate states. All this is represented in a design document.
4 participants
Added queries crate + Queries trait