Russ, The indexing that Oracle is supporting is 'index-on-expression'. DB2 also supports that, but it isnt enabled for character long columns, since they hadnt had a request for that. I talked to the DB2 server folks about these use-cases and they have agreed to support this via index-on-expression shortly. For the immediate needs, Rahul is going to look at supporting this via 'hidden' columns - Whenever there is a text field with an index specified, the backend will create a hidden and generated column (poplated with first X chars of the text field). The index will be created on this hidden column. When there is a lookup by value, the backend will actually do the lookup on the hidden indexed column. - you see any blockers to this ?
BTW, index is not turned ON on LogEntry.object_id. Do you feel this use-case usage is low to warrant that ? regards Mario
-- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@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.
