How to handle a migration that last too long for being deployed?

Hi everybody! I would like to know what options exist when you have a huge migration that will obviously not run on your productive server. I have spitted a model in two smaller ones and wrote then a migration to populate these new models. The number of original objects is around 250,000 and

Re: How to handle a migration that last too long for being deployed?

the second migration all the operations that are responsible for deleting the old model? This way, people trying to write will get an error - which is the best we can do here. Am I right? Thanks for your help! Cheers, Adrien Adrien Cossa wrote: Hi everybody! I would like to know what options exis

Re: Crazy Idea: OOP for "Hyperlink"

Hi, On 04/23/2018 10:59 AM, guettli wrote: I have a vague idea to use OOP for a hyperlink. A hyperlink has these attributes for me: - href - verbose name - Permission: Is the current user allowed to follow the link? - Preview (on-mouse-over tooltip) We have developed something similar in the