We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
First of all, this project is a great idea. Thanks!
From https://github.com/akaariai/django-reverse-unique/blame/f0dd7c01ae8ed6193a7ee26b7f4e4195ae42dadd/README.rst#L59-L60
current_salary = models.ReverseUnique( "EmployeeSalary", filter=Q(valid_from__gte=datetime.now) & (Q(valid_until__isnull=True) | Q(valid_until__lte=datetime.now)) )
aren't the valid_from and valid_until filters swapped so we can actually an employee's current salary?
valid_from
valid_until
current_salary = models.ReverseUnique( "EmployeeSalary", filter=Q(valid_from__lte=datetime.now) & (Q(valid_until__isnull=True) | Q(valid_until__gte=datetime.now)) )
The text was updated successfully, but these errors were encountered:
No branches or pull requests
First of all, this project is a great idea. Thanks!
From https://github.com/akaariai/django-reverse-unique/blame/f0dd7c01ae8ed6193a7ee26b7f4e4195ae42dadd/README.rst#L59-L60
aren't the
valid_from
andvalid_until
filters swapped so we can actually an employee's current salary?The text was updated successfully, but these errors were encountered: