On Sat, Jan 16, 2010 at 9:55 PM, Mat Clayton <[email protected]> wrote: > Thanks, I've looked over both sets of code, seem's fine to me. The only > complex stuff is that Indexes can only be created on certain field types, so > additional checks may need doing. Also different index types are available > on different storage engines, for MySQL. Would people want support for > selecting the index type and direction?
I'd say don't bother. If you *really* want to fine tune your database, you aren't going to use the ORM - you're going to use initial SQL defintions, or leave it up to your handy neighborhood db admin. On top of that, anything beyond a simple "CREATE INDEX foo ON bar (attr, attr)" is going to start walking into areas that are specific to individual databases. db_index=True has been sufficient for indexes of all types so far; I'm happy to continue the trend here. > Finally char field index lengths need to be considered, I'm assuming the > Meta field would have to take these into account as well. > Also have reopened a ticket http://code.djangoproject.com/ticket/5805 to > cover this Cheers. I should have known this had been suggested before :-) Yours, Russ Magee %-)
-- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
