Adrian Holovaty wrote: > Yeah, Django doesn't use SELECT * -- the field names are always > explicitly stated in all Django ORM underlying SQL statements. I add > fields to my models all the time and never have problems regarding > column order.
Good deal...I will refrain from fixing them all! *grin* As long as the gotchas are known (which are all outside of Django proper it appears), and the framework Does The Right Thing, it DOES certainly make things easier. And faster...migrating big tables through the "temp table...select into in right order...rename old table...rename new table" process can take a LOONG time in a db that supports transactions! > I appreciate the attention to detail in your bringing this up, though! :-D LOL! No worries...I'm just glad to be able to help a little bit. Now I just need to start dumping my notes into the wiki! --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
