On Mar 21, 2013, at 7:00 PM, Russell Keith-Magee <[email protected]> wrote:
> > In the case of PostgreSQL, I suspect there will also be some work required > constructing a full-text index on text columns -- optionally, since indices > aren't free to create, so they can't be turned on by default. This isn't really *that* hard to get around, it would just require another optional keyword argument to models.TextField and models.CharField (e.g. db_fulltext_column=True) and requisite documentation. I would expect that the biggest problem with implementing something like this would be that MySQL is going to be a tough cookie to address. InnoDB supports foreign key constraints but not full-text indexing, while MyISAM supports full-text indexing but not foreign-key constraints. So, either you can have data integrity, or you can have full-text indexing, but not both. And what happens when someone defines one or the other in Django and expects it to actually work…? Best Regards, Luke Sneeringer -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
