Skip to content
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

Consistently use transactions to update database #866

Merged
merged 1 commit into from
Aug 10, 2019

Commits on Aug 9, 2019

  1. Consistently use transactions to update database

    For any action which is multi-step (requires updating more than 1 DB
    key), use transaction to make update atomic.
    
    Also pack big chunks of updates (importing packages for importing and
    mirror updates) into single transaction to improve aptly performance and
    get some isolation.
    
    Note that still layers up (Collections) provide some level of isolation,
    so this is going to shine with the future PRs to remove collection
    locks.
    
    Spin-off of aptly-dev#459
    smira committed Aug 9, 2019
    Configuration menu
    Copy the full SHA
    5b4f3bb View commit details
    Browse the repository at this point in the history