Re: [Django] #26926: Dual index migration bug?

[Django]

#26926: Dual index migration bug?
+--
 Reporter:  Vaal|Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  1.9
 Severity:  Normal  |   Resolution:  duplicate
 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 timgraham):

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


--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.0d0433f123d8f25d7f6e56894b29f549%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26926: Dual index migration bug?

[Django]

#26926: Dual index migration bug?
+--
 Reporter:  Vaal|Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.9
 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 Vaal):

 In version "1.11" on the 4 step, the index was created.

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.6012adf3ecf91f4c8558d1dcdc4e1114%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26926: Dual index migration bug?

[Django]

#26926: Dual index migration bug?
+--
 Reporter:  Vaal|Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.9
 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 Vaal:

Old description:

> Example:
>
> 1) Added new field to model
> x_index = models.BooleanField(default=True, db_index=True, unique=True)
> There is an unnecessary index. But the conditions of the situation.
>
> 2) Create and run the migration.
> In the database this field will have only one index - unique.
>
> 3) Change the field.
> x_index = models.BooleanField(default=True, db_index=True)
> Remove the unique index.
>
> 4) Create and run the migration.
> Now, this field doesn't have of any indexes in database.

New description:

 Example:

 1) Added new field to model
 x_index = models.BooleanField(default=True, db_index=True, unique=True)
 There is an unnecessary index. But the conditions of the situation.

 2) Create and run the migration.
 In the database this field will have only one index - unique.

 3) Change the field.
 x_index = models.BooleanField(default=True, db_index=True)
 Remove the unique index.

 4) Create and run the migration.
 Now, this field doesn't have of any indexes in database.

 p.s. Mysql database

--

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.b4af6e0543e6e42855698cc76ce28c38%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26926: Dual index migration bug?

[Django]

#26926: Dual index migration bug?
+--
 Reporter:  Vaal|Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.9
 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 Vaal):

 Bug reproduced in 1.10 RC1

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.c0a29ae6c8aabb7a8fe4ab8249ad4763%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26926: Dual index migration bug?

[Django]

#26926: Dual index migration bug?
+--
 Reporter:  Vaal|Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.9
 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 jdufresne):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Can you test on master? I believe this was fixed by commit:
 
[https://github.com/django/django/commit/9356f63a99957f01c14a9788617428a172a29fcb
 9356f63a99957f01c14a9788617428a172a29fcb]

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.568961742b41424fa5b1f87f2b384b85%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26926: Dual index migration bug?

[Django]

#26926: Dual index migration bug?
+--
 Reporter:  Vaal|Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  1.9
 Severity:  Normal  |   Resolution:  needsinfo
 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 charettes):

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


Comment:

 A lot of fixes have been submitted for similar issues in the 1.10 release
 cycle.

 Please confirm the issue is still present using
 [https://www.djangoproject.com/download/ 1.10 RC1] and re-open this ticket
 if it's the case.

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.72e0135fccdfc1a017b8a3643dc37d92%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #26926: Dual index migration bug?

[Django]

#26926: Dual index migration bug?
+
 Reporter:  Vaal|  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Migrations  |Version:  1.9
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 Example:

 1) Added new field to model
 x_index = models.BooleanField(default=True, db_index=True, unique=True)
 There is an unnecessary index. But the conditions of the situation.

 2) Create and run the migration.
 In the database this field will have only one index - unique.

 3) Change the field.
 x_index = models.BooleanField(default=True, db_index=True)
 Remove the unique index.

 4) Create and run the migration.
 Now, this field doesn't have of any indexes in database.

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/047.2f2b7df1893c8c206b8811589075750a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.