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.

Sign up for GitHub

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

Jump to bottom

Fix #479 -- Make sure db_default is being considered #502

Merged
merged 5 commits into from
Sep 26, 2024
Merged

Fix #479 -- Make sure db_default is being considered #502

merged 5 commits into from
Sep 26, 2024

Commits on Sep 17, 2024

  1. Make sure db_default is being considered as a default value

    @berinhard
    berinhard committed Sep 17, 2024
    Configuration menu
    Copy the full SHA
    517413f View commit details
    Browse the repository at this point in the history

  2. Add condition to only enforce this test on Django>=5.0

    @berinhard
    berinhard committed Sep 17, 2024
    Configuration menu
    Copy the full SHA
    fdc7ae3 View commit details
    Browse the repository at this point in the history

  3. Get db_default using getattr 

    This is necessary since this field attribute does not exist in Django versions
older than 5.0
    @berinhard
    berinhard committed Sep 17, 2024
    Configuration menu
    Copy the full SHA
    cc9f999 View commit details
    Browse the repository at this point in the history

  4. Update the changelog

    @berinhard
    berinhard committed Sep 17, 2024
    Configuration menu
    Copy the full SHA
    1eab74c View commit details
    Browse the repository at this point in the history

Commits on Sep 26, 2024

  1. Merge branch 'main' into issue479

    @berinhard
    berinhard committed Sep 26, 2024
    Configuration menu
    Copy the full SHA
    99d5dfb View commit details
    Browse the repository at this point in the history