Re: Capturing faked migrations in django_migrations table

Awesome, thank you very much for the detailed answer. -Steve On Tue, May 19, 2015 at 4:16 PM, Shai Berger wrote: > Hi Steve, > > On Wednesday 20 May 2015 01:50:15 steve byerly wrote: > > > > I'm also unclear what the argument against storing in the migrations > table > > is

Re: Capturing faked migrations in django_migrations table

Hi Steve, On Wednesday 20 May 2015 01:50:15 steve byerly wrote: > > I'm also unclear what the argument against storing in the migrations table > is vs logging them - honest question. Since I have 4 web servers, the > information would be logged to any one of them - depending on which > executed

Re: Capturing faked migrations in django_migrations table

Sorry all, i didn't get notified of the replies. I guess I assumed that since you are already capturing the applied migrations in the database, why not also capture if it was faked or not? In the case I outlined in the original post, there were initial migrations (0001, 0002, 0003) and new

Re: Looking for Django mentor to help with an ongoing project.

Hi, this mailing list is about the development of django itself, please post to django-users instead. Em terça-feira, 19 de maio de 2015 12:25:13 UTC-3, SB escreveu: > > Hi, > We are a group of students and are putting together a website

Looking for Django mentor to help with an ongoing project.

Hi, We are a group of students and are putting together a website in Django. Our experience with Django is somewhat limited and we are looking for someone with experience in Django that would be able to review what we did and give us feedback and tips on what the best approach would be. --