Sure - setting it up is easy. There are hard questions about database mutations however. If you drop column bar from table Fubar, then the old code is still querying for buth Fu and Bar:
SELECT id, fu, bar FROM fubar .... On-premise, this is the case for maybe 10 seconds, tops. In the cloud, this could be the case for 30 minutes. We've decided that this is the developers responsibility, and not the responsibility of DevOps CI/CD, just like the developer needs to either use cache-busting techniques when changing JS and CSS, or educate his users to press Shift-F5 when things go wrong. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/6cd917c1-814d-4839-9849-898ff03618c9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
