Make the required changes into the db and keep up-to-date the archiver's tests.
Details
Details
- Reviewers
ardumont - Group Reviewers
Reviewers - Commits
- rDSTOC5c8085d1785b: Update the archiver for the new db shema
rDSTOC9451c5f4b83f: Use postgres 9.5's functions for jsonb manipulation
R65:5c8085d1785b: Update the archiver for the new db shema
R65:9451c5f4b83f: Use postgres 9.5's functions for jsonb manipulation
rDSTO9451c5f4b83f: Use postgres 9.5's functions for jsonb manipulation
rDSTO5c8085d1785b: Update the archiver for the new db shema
Diff Detail
Diff Detail
- Repository
- rDSTO Storage manager
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
Event Timeline
swh/storage/archiver/storage.py | ||
---|---|---|
74–82 | directly For jsonb manipulation btw https://www.postgresql.org/docs/9.5/static/functions-json.html. | |
swh/storage/archiver/worker.py | ||
130 | its mtime | |
swh/storage/db.py | ||
665 | Retrieve | |
684 | '... its mtime...' | |
690–691 | As this is a first draft, i imagine that you'll update the docstring later. |
Comment Actions
This seems quite ok so far.
Submitted a first version for review, but there is still some work to do for the Jsonb access.
What do you mean?
The jsonb access for the update?
Comment Actions
Yes, I used the jsonb_set function to let postgres do the update.
- Use postgres 9.5's functions for jsonb manipulation
- Some typos corrections
swh/storage/db.py | ||
---|---|---|
695 | Indeed, postgres would not let us do that. |