Re: [Django] #30152: MySQL: "Cannot change column 'id': used in a foreign key constraint" when altering pk of model with ForeignKey to self

#30152: MySQL: "Cannot change column 'id': used in a foreign key constraint" when altering pk of model with ForeignKey to self ---+ Reporter: Carsten Fuchs |Owner: nobody Type: Bug|

Re: [Django] #30152: MySQL: "Cannot change column 'id': used in a foreign key constraint" when altering pk of model with ForeignKey to self

#30152: MySQL: "Cannot change column 'id': used in a foreign key constraint" when altering pk of model with ForeignKey to self ---+- Reporter: Carsten Fuchs |Owner: nobody Type: Bug|

Re: [Django] #30152: MySQL: "Cannot change column 'id': used in a foreign key constraint" when altering pk of model with ForeignKey to self (was: MySQL: Cannot change column 'id': used in a foreign ke

#30152: MySQL: "Cannot change column 'id': used in a foreign key constraint" when altering pk of model with ForeignKey to self ---+- Reporter: Carsten Fuchs |Owner: nobody Type: Bug|

Re: [Django] #30152: MySQL: Cannot change column 'id': used in a foreign key constraint

#30152: MySQL: Cannot change column 'id': used in a foreign key constraint ---+-- Reporter: Carsten Fuchs |Owner: nobody Type: Bug| Status: closed Component: Mig

Re: [Django] #30152: MySQL: Cannot change column 'id': used in a foreign key constraint

#30152: MySQL: Cannot change column 'id': used in a foreign key constraint ---+-- Reporter: Carsten Fuchs |Owner: nobody Type: Bug| Status: closed Component: Mig

Re: [Django] #30152: MySQL: Cannot change column 'id': used in a foreign key constraint

#30152: MySQL: Cannot change column 'id': used in a foreign key constraint ---+-- Reporter: Carsten Fuchs |Owner: nobody Type: Bug| Status: closed Component: Mig

Re: [Django] #30152: MySQL: Cannot change column 'id': used in a foreign key constraint

#30152: MySQL: Cannot change column 'id': used in a foreign key constraint ---+-- Reporter: Carsten Fuchs |Owner: nobody Type: Bug| Status: closed Component: Mig

Re: [Django] #30152: MySQL: Cannot change column 'id': used in a foreign key constraint

#30152: MySQL: Cannot change column 'id': used in a foreign key constraint ---+-- Reporter: Carsten Fuchs |Owner: nobody Type: Bug| Status: closed Component: Mig

Re: [Django] #30152: MySQL: Cannot change column 'id': used in a foreign key constraint

#30152: MySQL: Cannot change column 'id': used in a foreign key constraint -+- Reporter: Carsten Fuchs|Owner: nobody Type: Uncategorized| Status: new C

[Django] #30152: MySQL: Cannot change column 'id': used in a foreign key constraint

#30152: MySQL: Cannot change column 'id': used in a foreign key constraint -+- Reporter: Carsten| Owner: nobody Fuchs | Type: |

Re: [Django] #30150: Django 1.11 with MySQL 8: "Unknown system variable 'TX_ISOLATION'"

#30150: Django 1.11 with MySQL 8: "Unknown system variable 'TX_ISOLATION'" -+- Reporter: Carsten Fuchs|Owner: nobody Type: Bug | Status: closed

Re: [Django] #30150: Django 1.11 with MySQL 8: "Unknown system variable 'TX_ISOLATION'"

#30150: Django 1.11 with MySQL 8: "Unknown system variable 'TX_ISOLATION'" -+- Reporter: Carsten Fuchs|Owner: nobody Type: Bug | Status: closed

Re: [Django] #30150: Django 1.11 with MySQL 8: "Unknown system variable 'TX_ISOLATION'"

#30150: Django 1.11 with MySQL 8: "Unknown system variable 'TX_ISOLATION'" -+- Reporter: Carsten Fuchs|Owner: nobody Type: Bug | Status: new C

Re: [Django] #30151: QuerySet.last() and [] operator give different results (was: last() and [] operator give different results)

#30151: QuerySet.last() and [] operator give different results -+- Reporter: NMO13|Owner: nobody Type: Bug | Status: closed Component:

Re: [Django] #30151: last() and [] operator give different results

#30151: last() and [] operator give different results ---+-- Reporter: NMO13 |Owner: nobody Type: Uncategorized | Status: new Component: Uncategorized |

Re: [Django] #30151: last() and [] operator give different results

#30151: last() and [] operator give different results ---+-- Reporter: NMO13 |Owner: nobody Type: Uncategorized | Status: new Component: Uncategorized |

[Django] #30151: last() and [] operator give different results

#30151: last() and [] operator give different results -+ Reporter: NMO13 | Owner: nobody Type: Uncategorized | Status: new Component: Uncategorized |

Re: [Django] #30128: Using database functions with tzinfo=datetime.timezone(datetime.timedelta(...)) results in an incorrect query

#30128: Using database functions with tzinfo=datetime.timezone(datetime.timedelta(...)) results in an incorrect query -+- Reporter: mvarnar |Owner: Can

Re: [Django] #30064: Admin search with a null character crashes with "A string literal cannot contain NUL (0x00) characters." on PostgreSQL

#30064: Admin search with a null character crashes with "A string literal cannot contain NUL (0x00) characters." on PostgreSQL ---+--- Reporter: kenichi-cc |Owner: Can Sarıgöl Type: Bug

[Django] #30150: Django 1.11 with MySQL 8: "Unknown system variable 'TX_ISOLATION'"

#30150: Django 1.11 with MySQL 8: "Unknown system variable 'TX_ISOLATION'" -+- Reporter: Carsten| Owner: nobody Fuchs | Type: Bug|

Re: [Django] #18012: Propagate reverse foreign keys from proxy models to base class

#18012: Propagate reverse foreign keys from proxy models to base class -+- Reporter: Anssi Kääriäinen |Owner: Simon Type: | Charette Cleanup/optimization

Re: [Django] #28687: Add a 'Not Empty' option to admin's related filter

#28687: Add a 'Not Empty' option to admin's related filter -+- Reporter: Brillgen Developers |Owner: Jake Type: | Barber Cleanup/optimization |

Re: [Django] #30149: Empty value selected check in Admin Filter prevents subclassing (was: "Empty value selected check in Admin Filter prevents subclassing")

#30149: Empty value selected check in Admin Filter prevents subclassing -+- Reporter: Sardorbek Imomaliev |Owner: nobody Type: Uncategorized| Status: new Comp

[Django] #30149: "Empty value selected check in Admin Filter prevents subclassing"

#30149: "Empty value selected check in Admin Filter prevents subclassing" ---+ Reporter: Sardorbek Imomaliev | Owner: nobody Type: Uncategorized| Status: new