Ah. Thanks for the correction! :) L
On Mar 21, 2013, at 9:13 PM, Karen Tracey <[email protected]> wrote: > On Thu, Mar 21, 2013 at 9:51 PM, Luke Sneeringer <[email protected]> wrote: > 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…? > > Django already supports full-text index searching on MySQL: > https://docs.djangoproject.com/en/1.5/ref/models/querysets/#search > > The issue of creating the index is handled by punting to the user -- doc > notes you've got to create the full-text index yourself. > > Karen > > -- > 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. > > -- 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.
