Re: [Django] #27558: Setting db_index=False on existing ForeignKey causes constraint to be recreated on MySQL

2016-12-15 Thread Django
#27558: Setting db_index=False on existing ForeignKey causes constraint to be recreated on MySQL -+- Reporter: Ed Morley|Owner: Ed Morley Type: Bug |

Re: [Django] #27558: Setting db_index=False on existing ForeignKey causes constraint to be recreated on MySQL

2016-12-15 Thread Django
#27558: Setting db_index=False on existing ForeignKey causes constraint to be recreated on MySQL -+- Reporter: Ed Morley|Owner: Ed Morley Type: Bug |

Re: [Django] #27558: Setting db_index=False on existing ForeignKey causes constraint to be recreated on MySQL

2016-12-01 Thread Django
#27558: Setting db_index=False on existing ForeignKey causes constraint to be recreated on MySQL -+- Reporter: Ed Morley|Owner: Ed Morley Type: Bug |

Re: [Django] #27558: Setting db_index=False on existing ForeignKey causes constraint to be recreated on MySQL

2016-12-01 Thread Django
#27558: Setting db_index=False on existing ForeignKey causes constraint to be recreated on MySQL -+- Reporter: Ed Morley|Owner: Ed Morley Type: Bug |

Re: [Django] #27558: Setting db_index=False on existing ForeignKey causes constraint to be recreated on MySQL

2016-12-01 Thread Django
#27558: Setting db_index=False on existing ForeignKey causes constraint to be recreated on MySQL -+- Reporter: Ed Morley|Owner: Ed Morley Type: Bug |

Re: [Django] #27558: Setting db_index=False on existing ForeignKey causes constraint to be recreated on MySQL (was: Setting db_index=False on existing ForeignKey causes constraint to be recreated)

2016-11-30 Thread Django
#27558: Setting db_index=False on existing ForeignKey causes constraint to be recreated on MySQL -+- Reporter: Ed Morley|Owner: nobody Type: Bug |