#28286: Union ("|") and Interception ("&") QuerySets raise AssertionError
---------------------------------+--------------------------------------
Reporter: AbrahamGo | Owner: (none)
Type: Bug | Status: new
Component: Error reporting | Version:
Severity: Normal | Resolution:
Keywords: QuerySets, 1.7 | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+--------------------------------------
Description changed by AbrahamGo:
Old description:
> We are currently working in a migration from {{{Django 1.5.12}}} to
> {{{1.7.11}}} and we are currently receiving the following error in
> {{{Django 1.7.11}}} when we are using union ("**|**") or interception
> ("**&**" ) between {{{QuerySets}}}, for example {{{queryset_c =
> queryset_a | queryset_b}}}.
> {{{
> AssertionError: assert set(['T6', 'T...encyaccount']) == set([])
> Extra items in the left set:
> 'clients_client'
> 'reconciliation_asset'
> 'T8'
> 'T6'
> 'settlements_currencyaccount'
> 'core_entity'
> Use -v to get the full diff
> }}}
>
> Investigating we have noticed that it's a bug fixed in {{{Django 1.8.5}}}
> but we need to know if there is any work around to this issue in
> {{{Django 1.7.11}}} or we should redo this logic to avoid use "**|**"
> and "**&**" operators.
>
> Could you let me know if there is any work around please?
>
> Thanks.
New description:
We are currently working to migrate a project from {{{Django 1.5.12}}} to
{{{1.7.11}}} and we are currently receiving the following error in
{{{Django 1.7.11}}} when we are using union ("**|**") or interception
("**&**" ) between {{{QuerySets}}}, for example {{{queryset_c =
queryset_a | queryset_b}}}.
{{{
AssertionError: assert set(['T6', 'T...encyaccount']) == set([])
Extra items in the left set:
'clients_client'
'reconciliation_asset'
'T8'
'T6'
'settlements_currencyaccount'
'core_entity'
Use -v to get the full diff
}}}
Investigating we have noticed that it's a bug fixed in {{{Django 1.8.5}}}
but we need to know if there is any work around to this issue in {{{Django
1.7.11}}} or we should redo this logic to avoid use "**|**" and "**&**"
operators.
Could you let me know if there is any work around please?
Thanks.
--
--
Ticket URL: <https://code.djangoproject.com/ticket/28286#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.70ff169554400c531bba4bee763f69dc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
