On Sun, 2009-08-02 at 21:01 -0700, Rusty Greer wrote: > i added a column to one of my tables in my db. i added the column in > the model definition, then i went into mysql and added the column with > what i think is the appropriate alter table command. > the command i used was: > alter table db_game add column player_info_url varchar(200) not null; > > the code in the model is this: > player_info_url = models.URLField(blank=True) > > i am now able to update that table no problem from mysql. the new > field shows up just fine in the admin. i can edit other tables via > the admin, however, if i change the table i modified in the admin (not > just the new field), the development server seems to lock up. after i > restart it, all is fine until i edit that same table again.
Locking up is a rare and unusual symptom. There's one intermediate test you haven't done (you've tried direct db editing and end-to-end through the web browser): can you query and edit the records via the interactive prompt? Another thing I would try is creating a copy of your settings file then modifying it to point to a database with a different name and trying a fresh install (so you aren't blowing away your current database). Then see if the problem reoccurs. You can also compare the sql from the two if there are differences in behaviour. > > i am not too concerned about the development server, i can nuke my db > and restart with that and i am sure the problem will go away. > however, when i go try to make the same change on my production > server, i don't want to have the same problems with it. any ideas > what i could have possibly done wrong? or how to fix it? will i have > the same problem with apache/wsgi on my production server. > > by the way i am running 1.0.2-final and mysql One important piece of debugging would be to upgrade to 1.0.3 as soon as you can, since there are about 6 months worth of bug fixes in there. I can't think of anything that's been added in the 1.0.X branch that would change this (the whole behaviour sounds *very * odd), but it wouldn't hurt to rule that out. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
