I'm facing the same speed issue here. Like Andrew mentioned above, if
initial data is going to be removed and data migrations are the way
forward, even having an option to skip migrations is a problem because we'd
need that data to be populated. Is there something planned for this for
Django 1.
Any updates on this? I also want to take a crack at this and think its best
to not duplicate efforts. Let me know how I can pitch in.
On Wednesday, April 22, 2015 at 10:25:17 PM UTC+5:30, Kevin Glavin wrote:
>
> Thank you everyone for your interest. I spoke with Tim last night to start
> piecin
