Latest wisdom on 'small migrations'

Given that Syncdb won't ever issue an alter table command ('no such
column'), that <a href="http://code.djangoproject.com/wiki/
SchemaEvolution">Schema Evolution is still in debate</a>, that <a
href="http://south.aeracode.org/">South</a> is a bit of an overhead if
all you want to do is add a field to an existing model - one column to
a table, and that manually adding this to an existing database (e.g.
sqlite which will add a column but not rename one) <a href="http://
groups.google.com/group/django-users/browse_thread/thread/
6e29ea32d8f11531/db42fe72b464aca2?lnk=gst&q=add+a+field+to+a
+table#db42fe72b464aca2">is a fiddle</a>, how would you suggest the
easiest way of adding one (overlooked) column to an existing table to
enable a new field in an existing model when the database is already
full of data? Given that gui database browsers are also in the picture
(e.g. <a href="http://www.google.co.uk/url?
sa=t&source=web&cd=1&ved=0CB0QFjAA&url=https%3A%2F%2Faddons.mozilla.org
%2Fen-US%2Ffirefox%2Faddon
%2F5817%2F&ei=7qkKTLUcof7SBJbYlWM&usg=AFQjCNEZtAsOR_YRbiExOgyBLR2vMS9bLw&sig2=6xf9OD42BXoV89b_tsqAPw">SQLite
Manager</a> for Firefox).

--
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+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.