Hi. The new index_together feature is great, but I think it's best to create an index on a table AFTER the table is filled, and assuming there won't be many new inserts. But in django, syncdb creates the index at the same time the table is created, and of course, the table is initially empty. How does django deal with this? Does it know to drop the index before inserting new records and re-create the index afterwards?
If not, can I syncdb, drop the index manually in mysql, populate the table, then re-create the index manually (as long as I use the same index name that django chose)? Will django be none-the-wiser if I do this? -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/gBx54Nzn5X8J. 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.
