Re: [Django] #34926: Missing model after squashing

[Django]

#34926: Missing model after squashing
+--
 Reporter:  Sebastian Jekutsch  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  4.2
 Severity:  Normal  |   Resolution:  invalid
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by Sebastian Jekutsch):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 Ok, seems I have differences locally.

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018b637056bf-895d9576-3cdd-42b2-a2b3-3a9bd56eb377-00%40eu-central-1.amazonses.com.

Re: [Django] #34926: Missing model after squashing

[Django]

#34926: Missing model after squashing
+--
 Reporter:  Sebastian Jekutsch  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  4.2
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by Mariusz Felisiak):

 Replying to [comment:3 Sebastian Jekutsch]:
 > Right, but it's below its first reference in model Topic within the
 script, so an initial database migration will raise an "ValueError:
 Related model 'knowledgebase.activity' cannot be resolved".
 > (Apologize for not stating the problem more specific.)

 That is also not true:
 {{{
 migrations.CreateModel(
 name="Activity",
 fields=[
 (
 "id",
 models.BigAutoField(
 auto_created=True,
 primary_key=True,
 serialize=False,
 verbose_name="ID",
 ),
 ),
 ("name", models.CharField(max_length=50)),
 (
 "members",
 models.ManyToManyField(
 blank=True,
 related_name="memberships",
 to="knowledgebase.activity",
 ),
 ),
 ("alternative_names", models.CharField(blank=True,
 max_length=250)),
 ],
 options={
 "verbose_name": "Activity",
 "verbose_name_plural": "Activities",
 "ordering":
 [django.db.models.functions.text.Lower("name")],
 },
 ),
 migrations.AddField(
 model_name="topic",
 name="activities",
 field=models.ManyToManyField(
 blank=True, related_name="activities",
 to="knowledgebase.activity"
 ),
 ),
 }}}

 Please see TicketClosingReasons/UseSupportChannels for ways to get help
 and don't use Trac as a support channel.

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018b635fd98f-5f8f54dc-0a4b-47b7-bf1d-f97dc411c4e0-00%40eu-central-1.amazonses.com.

Re: [Django] #34926: Missing model after squashing

[Django]

#34926: Missing model after squashing
+--
 Reporter:  Sebastian Jekutsch  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  4.2
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by Sebastian Jekutsch):

 * status:  closed => new
 * resolution:  invalid =>


Comment:

 Right, but it's below its first reference in model Topic within the
 script, so an initial database migration will raise an "ValueError:
 Related model 'knowledgebase.activity' cannot be resolved".
 (Apologize for not stating the problem more specific.)

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018b635465b9-433862dc-1a59-4b89-bd3a-8bd3fe4ae863-00%40eu-central-1.amazonses.com.

Re: [Django] #34926: Missing model after squashing

[Django]

#34926: Missing model after squashing
+--
 Reporter:  Sebastian Jekutsch  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  4.2
 Severity:  Normal  |   Resolution:  invalid
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by Mariusz Felisiak):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 `Activity` is in the squashed migration.

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018b62de1c78-89ad133e-2775-4137-ae8c-dffceeca1f0f-00%40eu-central-1.amazonses.com.

Re: [Django] #34926: Missing model after squashing

[Django]

#34926: Missing model after squashing
+--
 Reporter:  Sebastian Jekutsch  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  4.2
 Severity:  Normal  |   Resolution:
 Keywords:  | 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 Sebastian Jekutsch:

Old description:

> Sorry for an unspecific subject and not searching for duplicates due to
> lack of knowledge, understanding and time.
>
> As an excerpt from #34924 which has been correctly closed as duplicate
> for two of its issues, the third one remains unresolved, as far as I see.
> I reopen it with this new report.
>
> Based on the attachments
> 1. Zip of single migrations 0001 to 0116
> 2. Resulting squashed migration file of "manage.py squashmigrations
> knowledgebase 0116"
> 3. models.py at the end of 0116
> I found that model Activity has errorneously disappeared completely in
> the squashed migration file. It has even not been detected by a new
> makemigrations run for cross-check.

New description:

 Sorry for an unspecific subject and not searching for duplicates due to
 lack of knowledge, understanding and time.

 As an excerpt from #34924 which has been correctly closed as duplicate for
 two of its issues, the third one remains unresolved, as far as I see. I
 reopen it with this new report.

 Based on the attachments
 1. Zip of single migrations 0001 to 0116
 2. Resulting squashed migration file of "manage.py squashmigrations
 knowledgebase 0116"
 3. models.py at the end of 0116
 within #34924,
 I found that model Activity has errorneously disappeared completely in the
 squashed migration file. It has even not been detected by a new
 makemigrations run for cross-check.

--

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018b62aebe68-e383ece9-7ffb-414a-8987-0bba03e58c48-00%40eu-central-1.amazonses.com.

[Django] #34926: Missing model after squashing

[Django]

#34926: Missing model after squashing
--+
   Reporter:  Sebastian Jekutsch  |  Owner:  nobody
   Type:  Bug | Status:  new
  Component:  Migrations  |Version:  4.2
   Severity:  Normal  |   Keywords:
   Triage Stage:  Unreviewed  |  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+
 Sorry for an unspecific subject and not searching for duplicates due to
 lack of knowledge, understanding and time.

 As an excerpt from #34924 which has been correctly closed as duplicate for
 two of its issues, the third one remains unresolved, as far as I see. I
 reopen it with this new report.

 Based on the attachments
 1. Zip of single migrations 0001 to 0116
 2. Resulting squashed migration file of "manage.py squashmigrations
 knowledgebase 0116"
 3. models.py at the end of 0116
 I found that model Activity has errorneously disappeared completely in the
 squashed migration file. It has even not been detected by a new
 makemigrations run for cross-check.

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018b62acb52f-4825f0dd-614f-4c70-8b86-3a19eed96e73-00%40eu-central-1.amazonses.com.