If you're interested in something _much_ nicer than phpMyAdmin and you're on OS X, check out Querious or Sequel Pro. I've found Django development about 25% more enjoyable since switching from browser- based software to desktop software for database management (both local and remote).
David On Aug 25, 1:46 pm, "!!CONDORIOUS!!" <condor.c...@gmail.com> wrote: > I am constantly updating the database model. I have tried South but > still feel like the simplest most intuitive way to update a update an > existing project's database is to manually create the fields using > phpMyAdmin. Two steps > > 1. Add/Update field model.py > 2. Add/Update in database to match (phpMyAdmin makes life so much simpler). > > On Tue, Aug 24, 2010 at 6:22 PM, Sells, Fred > > > > > > <fred.se...@adventistcare.org> wrote: > > During development phase, I actually drop and recreate my database, then run > > syncdb etc to make sure I’ve got a clean start. Probably not practical once > > I get into production. > > > From: django-users@googlegroups.com [mailto:django-us...@googlegroups.com] > > On Behalf Of Nick Arnett > > Sent: Tuesday, August 24, 2010 10:57 AM > > To: django-users@googlegroups.com > > Subject: Re: manage.py syncdb not working > > > On Tue, Aug 24, 2010 at 7:43 AM, Sithembewena Lloyd Dube <zebr...@gmail.com> > > wrote: > > > Thanks Reinout. I have been seeing a lot of discussions regarding South > > lately - time to dive in and find out what it is and what it means for me. > > > I was under the impression that Django would add a field to my table. So, is > > syncdb only good during initial database setup? > > > That is essentially correct, though I have modified tables by renaming the > > old one, letting syncdb recreate it, then copy the old data into the new > > table. However, due to foreign keys, that's not as simple as it might > > sound. Early in development, I have also let syncdb create a whole new > > database, then copied the old data into it. > > > Come to think of it, I have also sometimes created a modified table under a > > temporary name, so that I can see what Django would have done if it were a > > new setup, so that I can modify the old table manually to match how Django > > would have done it automatically (and then drop the temporary table). > > > Nick > > > -- > > You received this message because you are subscribed to the Google Groups > > "Django users" group. > > To post to this group, send email to django-us...@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. > > > -- > > You received this message because you are subscribed to the Google Groups > > "Django users" group. > > To post to this group, send email to django-us...@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. > > -- > Condor > 310.951.1177 > condor.c...@gmail.com > > :%s/war/peace/g -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
