Sync history #109

New issue

Closed

opened 2026-05-10 19:38:45 +00:00 by aniram · 0 comments

aniram commented

2026-05-10 19:38:45 +00:00

Owner

The offline API does not return data on the history of propositions.

After running the daily cronjob which updates all tables check which propositions changed their status(ultimoStatus) and for those who did fetch their entire history(tramitacao) through the API respecting the Retry-After header. This presumes there exists already a table called proposition_history which will be appended to with the latest state for each proposition that changed.
Originally posted by @aniram in overdrives/cidadon#34 (comment)

TODO

Fetch history of all propositions from 2001 until the current year
During the daily sync compare each proposition's newly reported latest state with the one stored on the DB, if they differ sync the history for this specific proposition.

The offline API does not return data on the history of propositions. After running the daily cronjob which updates all tables check which propositions changed their status(ultimoStatus) and for those who did fetch their entire history(tramitacao) through the API respecting the Retry-After header. This presumes there exists already a table called proposition_history which will be appended to with the latest state for each proposition that changed. _Originally posted by @aniram in https://git.marinabsa.com/overdrives/cidadon/issues/34#issuecomment-857_ TODO - [x] Fetch history of all propositions from 2001 until the current year - [x] During the daily sync compare each proposition's newly reported latest state with the one stored on the DB, if they differ sync the history for this specific proposition.

aniram added this to the 2026.1 milestone

2026-05-10 19:38:50 +00:00

aniram added this to the Release 2026.1 project

2026-05-10 19:38:55 +00:00

aniram added the

Priority

High

label

2026-05-17 18:53:34 +00:00

aniram closed this issue

2026-06-13 16:53:26 +00:00

aniram added reference feature/sync-history