Re: [Django] #23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value

2023-10-19 Thread Django
#23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value -+ Reporter: Chris Woytowitz |Owner: vrocha Type: Bug |

Re: [Django] #23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value

2023-09-27 Thread Django
#23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value -+ Reporter: Chris Woytowitz |Owner: (none) Type: Bug |

Re: [Django] #23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value

2023-07-31 Thread Django
#23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value -+ Reporter: Chris Woytowitz |Owner: (none) Type: Bug |

Re: [Django] #23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value

2023-06-12 Thread Django
#23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value -+ Reporter: Chris Woytowitz |Owner: (none) Type: Bug |

Re: [Django] #23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value

2023-06-11 Thread Django
#23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value -+ Reporter: Chris Woytowitz |Owner: (none) Type: Bug |

Re: [Django] #23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value

2022-12-12 Thread Django
#23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value -+ Reporter: Chris Woytowitz |Owner: (none) Type: Bug |

Re: [Django] #23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value

2022-12-08 Thread Django
#23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value -+ Reporter: Chris Woytowitz |Owner: (none) Type: Bug |

Re: [Django] #23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value

2022-11-02 Thread Django
#23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value -+ Reporter: Chris Woytowitz |Owner: (none) Type: Bug |

Re: [Django] #23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value

2022-02-03 Thread Django
#23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value -+ Reporter: Chris Woytowitz |Owner: (none) Type: Bug |

Re: [Django] #23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value

2021-12-07 Thread Django
#23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value -+ Reporter: Chris Woytowitz |Owner: (none) Type: Bug |

Re: [Django] #23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value

2021-09-26 Thread Django
#23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value -+ Reporter: Chris Woytowitz |Owner: (none) Type: Bug |

Re: [Django] #23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value

2019-10-04 Thread Django
#23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value -+ Reporter: Chris Woytowitz |Owner: (none) Type: Bug |

Re: [Django] #23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value

2019-10-04 Thread Django
#23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value -+ Reporter: Chris Woytowitz |Owner: (none) Type: Bug |

Re: [Django] #23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value

2019-09-17 Thread Django
#23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value -+ Reporter: Chris Woytowitz |Owner: (none) Type: Bug |

Re: [Django] #23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value

2019-06-07 Thread Django
#23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value -+ Reporter: Chris Woytowitz |Owner: (none) Type: Bug |

Re: [Django] #23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value

2019-05-21 Thread Django
#23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value -+ Reporter: Chris Woytowitz |Owner: (none) Type: Bug |

Re: [Django] #23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value

2019-05-21 Thread Django
#23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value -+ Reporter: Chris Woytowitz |Owner: (none) Type: Bug |

Re: [Django] #23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value

2019-05-20 Thread Django
#23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value -+ Reporter: Chris Woytowitz |Owner: (none) Type: Bug |

Re: [Django] #23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value

2019-02-12 Thread Django
#23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value -+ Reporter: Chris Woytowitz |Owner: (none) Type: Bug |

Re: [Django] #23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value

2018-04-03 Thread Django
#23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value -+ Reporter: Chris Woytowitz |Owner: (none) Type: Bug |

Re: [Django] #23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value

2018-02-01 Thread Django
#23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value -+ Reporter: Chris Woytowitz |Owner: (none) Type: Bug |

Re: [Django] #23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value

2017-11-16 Thread Django
#23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value -+ Reporter: Chris Woytowitz |Owner: (none) Type: Bug |

Re: [Django] #23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value

2017-10-03 Thread Django
#23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value -+ Reporter: Chris Woytowitz |Owner: (none) Type: Bug |

Re: [Django] #23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value

2016-09-20 Thread Django
#23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value + Reporter: CrimsonZen |Owner: Type: Bug | Status: new

Re: [Django] #23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value (was: RenameModel should rename indexes, constraints, sequences and tri

2016-05-26 Thread Django
#23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value + Reporter: CrimsonZen |Owner: Type: Bug | Status: new