I'm not a dev that contribute too many directly to Django Project, but aniway I use Django since 0.96, so here is my 2 cents.
While Clay's idea have many cool changes and is a really nice idea that should be evaluated I share more Tom's and Daniel's point. Any Django Developer on World that change between Django Versions should read release notes, and documentation on new stuff. Any Django Developer on World have knowledge enough on your applications to decide migrate or not migrate to a new Django Version (they do it all time with third part apps). Any conscient Django Developer will test change and will assert that change works. Change will be documented, with solutions provided, and will fix a five year old bug with a simple enough fix. With management commands we can check every field defined by a EmailField that need to be changed and create sql for that. So, Django Devs are not childs, they can handle that change. +1 on change this fields. Cheers, Felipe 'chronos' Prenholato. Linux User nº 405489 Home page: http://devwithpassion.com | http://chronosbox.org/blog Github: http://github.com/chronossc/ Twitter: http://twitter.com/chronossc 2012/3/16 Luciano Pacheco <lucm...@gmail.com> > > On Fri, Mar 16, 2012 at 10:05 AM, Carl Meyer <c...@oddbird.net> wrote: > [...] > > I am not sure whether this should happen as a separate step or not. In >> an ideal world, we would have a longer username field. In the real >> world, we have to balance the benefit against the cost, and requiring a >> schema migration from practically every Django installation on the >> planet would IMO be the most significant backwards-incompatible change >> Django has ever shipped, at least since Django 1.0. It is not at all >> clear to me that the status quo, bad as it is, is worse than this cure. >> > > I can't understand how bad is a database schema change. Almost all web > site/applications need to change they database schema. Ok, in some cases > there are people that don't update their databases, but I think this cases > aren't willing to update their version of software as well. > > If the installed a web site/app is too small to be afraid to update, the > database change will be fast enough to cause a minimal downtime. > > If the installed a web site/app is too big, the sysadmin/devops already > know how to couple with database schema changes. And it's likely that they > have a test/staging/validation environment to analyse the changes before > production. > > This current limitation doesn't bother me, but all this concerned about > database schema change does. :-) > > Regards, > -- > Luciano Pacheco > blog.lucmult.com.br > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to django-developers@googlegroups.com. > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
