Re: South - when to start?
On Sat, Feb 19, 2011 at 8:28 PM, Rainy wrote: > I was going to say the exact same thing. I can just add that anything > is fairly > easy with South - starting from the beginning, starting just before > 2nd > dev joins in, or even starting after other devs join. Wiping out old > migrations > is also easy. > > -Rainyday Yes. In fact, in our company we wiped out our South stuff and started over after almost two years (and many dozens of migrations across several apps). We have the history in git, and didn't need the overhead. When one app has over 70 migrations, unit testing becomes pretty daunting. All you have to do is wipe out the south_migrationhistory table and delete the migrations, and it's like it's South's first day on the job. It's great! Shawn -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: South - when to start?
On Feb 18, 10:59 am, ShawnMilo wrote: > Just to add my tiny bit to this: > > I say start with South right away. But when you're ready to deploy for the > first time, wipe it all and to another --initial. > > The reason is that South is awesome for letting you upgrade a production app > that isn't allowed to stop working. So at first deployment, it's nice to > start clean so you don't have all those extra migrations for each run of > your unittests, etc. > > Shawn I was going to say the exact same thing. I can just add that anything is fairly easy with South - starting from the beginning, starting just before 2nd dev joins in, or even starting after other devs join. Wiping out old migrations is also easy. -Rainyday -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: South - when to start?
Just to add my tiny bit to this: I say start with South right away. But when you're ready to deploy for the first time, wipe it all and to another --initial. The reason is that South is awesome for letting you upgrade a production app that isn't allowed to stop working. So at first deployment, it's nice to start clean so you don't have all those extra migrations for each run of your unittests, etc. Shawn -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: South - when to start?
I'm mostly looking for a solution which would work for front-end devs who start early in the process (some part of app is written and they may jump on the UI). I guess South before 2 is a must then. I heard it's dead simple, I guess a little practice in writing migrations will not kill me. Thanks zalun On 02/18/11 13:11, Grigoriy Petukhov wrote: > I have found nice way to do quick development on 1st and 2nd steps you > have mentioned. > > I've put following instructions in reset.sh: > * Drop database > * Create new database > * Run ./manage.py syncdb > * Generate sample data > > When I change some model then I just run reset.sh. That works even for > several developers. If you pull someone changes then you run reset.sh > and get actual database state. It really saves time because you do not > need to spend your time writing migrations for schema and data. > > Of course, this method is not good if generating sample data takes a > lot of time. In such case migrating could be better solution. > > On 18 фев, 16:24, Piotr Zalewa wrote: >> Where is the best moment to start with south? >> >> 1. The very beginning, as the first app added to the project? >> 2. At the moment when more devs will be involved? >> 3. When real data will start to show? >> >> I'm building a new system, I think the current model progress is about >> 20%, where 100% is the moment I will put the site on the server. I'm >> very close to point 2. >> >> zalun >> -- >> blog http://piotr.zalewa.info >> jobs http://webdev.zalewa.info >> twit http://twitter.com/zalun >> face http://facebook.com/zaloon > -- blog http://piotr.zalewa.info jobs http://webdev.zalewa.info twit http://twitter.com/zalun face http://facebook.com/zaloon -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: South - when to start?
I have found nice way to do quick development on 1st and 2nd steps you have mentioned. I've put following instructions in reset.sh: * Drop database * Create new database * Run ./manage.py syncdb * Generate sample data When I change some model then I just run reset.sh. That works even for several developers. If you pull someone changes then you run reset.sh and get actual database state. It really saves time because you do not need to spend your time writing migrations for schema and data. Of course, this method is not good if generating sample data takes a lot of time. In such case migrating could be better solution. On 18 фев, 16:24, Piotr Zalewa wrote: > Where is the best moment to start with south? > > 1. The very beginning, as the first app added to the project? > 2. At the moment when more devs will be involved? > 3. When real data will start to show? > > I'm building a new system, I think the current model progress is about > 20%, where 100% is the moment I will put the site on the server. I'm > very close to point 2. > > zalun > -- > blog http://piotr.zalewa.info > jobs http://webdev.zalewa.info > twit http://twitter.com/zalun > face http://facebook.com/zaloon -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: South - when to start?
On Feb 18, 7:28 pm, Tom Evans wrote: > On Fri, Feb 18, 2011 at 10:24 AM, Piotr Zalewa wrote: > > Where is the best moment to start with south? > > > 1. The very beginning, as the first app added to the project? > > 2. At the moment when more devs will be involved? > > 3. When real data will start to show? > > > I'm building a new system, I think the current model progress is about > > 20%, where 100% is the moment I will put the site on the server. I'm > > very close to point 2. > > > zalun > > Personally, I wouldn't bother until either you have more than one > person developing the code base, or when to update a model means > updating more than one database schema. Until you are at that point, > the benefit is not huge, but the cost remains the same. > > Cheers > > Tom Here is a nice discussion about using South, you might want to check it out: http://stackoverflow.com/questions/5021800/why-use-south-during-initial-development -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: South - when to start?
On 18 February 2011 21:24, Piotr Zalewa wrote: > Where is the best moment to start with south? > > 1. The very beginning, as the first app added to the project? > 2. At the moment when more devs will be involved? > 3. When real data will start to show? > now! (just start using it!) -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: South - when to start?
On Fri, Feb 18, 2011 at 10:24 AM, Piotr Zalewa wrote: > Where is the best moment to start with south? > > 1. The very beginning, as the first app added to the project? > 2. At the moment when more devs will be involved? > 3. When real data will start to show? > > I'm building a new system, I think the current model progress is about > 20%, where 100% is the moment I will put the site on the server. I'm > very close to point 2. > > zalun Personally, I wouldn't bother until either you have more than one person developing the code base, or when to update a model means updating more than one database schema. Until you are at that point, the benefit is not huge, but the cost remains the same. Cheers Tom -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
South - when to start?
Where is the best moment to start with south? 1. The very beginning, as the first app added to the project? 2. At the moment when more devs will be involved? 3. When real data will start to show? I'm building a new system, I think the current model progress is about 20%, where 100% is the moment I will put the site on the server. I'm very close to point 2. zalun -- blog http://piotr.zalewa.info jobs http://webdev.zalewa.info twit http://twitter.com/zalun face http://facebook.com/zaloon -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
