On Mon, 2009-12-21 at 02:42 -0700, Ian Kelly wrote: > On Sun, Dec 20, 2009 at 11:25 PM, Mario Briggs <mario.bri...@in.ibm.com> > wrote: > >> This is known. The Oracle notes [1] mention that TextFields cannot be > >> indexed. Since Oracle requires indexes for unique columns, this also > >> means they cannot be unique, although we should probably make that > >> explicit. It may also be worthwhile to check for this when the models > >> are validated. > >> > >> Ian > >> > >> [1] > >> http://docs.djangoproject.com/en/1.1/ref/databases/#textfield-limitations > > > > Ian, > > > > From the other post on admin views using Text, it surfaced that Oracle > > (the DB) does support function based indexes on LOB upto ~4K. So the > > backend does not support that i guess ? > > Not currently, no. And if I were to put in some work on improving on > the Oracle backend's support for filtering on TextFields, I would > concentrate first on fixing the query so that it correctly compares > the entire TextField and not just the first 4000 characters. > Unfortunately, I don't think any function-based index will help with > that.
But there exists dbms_lob package to help with that, specially this particular search case "dbms_lob.instr". Of course it still has some issues (PL/SQL limitations) that may apply. Oracle is very evil what comes to long text fields, there is just not good and support for them. -- Jani Tiainen -- 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.
