Raphael Gaschignard
Raphael Gaschignard
Several past issues also cover collation issues around slugs and the like, I feel like this is probably still an issue (or at least some more documentation needs to happen...
similar to #189 , we need to have better error handling for missing related names
I totally understand wanting this, but basically taggit is following how M2M models work in Django in general. This involves needing to save the "owning" model first (to have an...
I mentioned this in #682 but basically there are legit use cases for _not_ deleting these outright, but I think we could document simple solutions (or even provide a hook...
something to check, whether index renaming is cheap or not in the major SQL vendors (locking etc)
also whether the index renaming is actually safe? we want to make sure that deployments including this don't cause downtime. I'm also partial to outright not having the rename by...
Things to do on this one: - set things up to make `RemovedInXWarning`s instead be errors for testing on `djmain`. - concretise the existing index names when setting up the...
@utkarsh2827 could you confirm whether adding the `related_name` fixed your issue here? Though to be honest I feel like we should have a less obtuse error here...
(note to anyone wanting to fix this: we should add some assertion to code relying on `related_name` for cases where it's not set up)
This seems similar to #189 , though the use case is different, we really need to specialize the error on `related_name` issues