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

Fix ArrayAgg() behavior for django 5 #1693

Open
bctcvai opened this issue May 15, 2024 · 0 comments
Open

Fix ArrayAgg() behavior for django 5 #1693

bctcvai opened this issue May 15, 2024 · 0 comments
Milestone

Comments

@bctcvai
Copy link
Member

bctcvai commented May 15, 2024

From unit tests:

  /usr/local/lib/python3.10/dist-packages/django/contrib/postgres/aggregates/general.py:45: RemovedInDjango50Warning: In Django 5.0, ArrayAgg() will return None instead of an empty list if there are no rows. Pass default=None to opt into the new behavior and silence this warning or default=[] to keep the previous behavior.
    warnings.warn(self.deprecation_msg, category=RemovedInDjango50Warning
@bctcvai bctcvai added this to the 1.4.0 milestone May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant