Re: Implementing Full Text Search in Django --Ticket #3254

2013-03-21 Thread Karen Tracey
On Thu, Mar 21, 2013 at 9:51 PM, Luke Sneeringer 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

Re: Implementing Full Text Search in Django --Ticket #3254

2013-03-21 Thread Javier Guerra Giraldez
On Thu, Mar 21, 2013 at 8:51 PM, Luke Sneeringer wrote: > InnoDB supports foreign key constraints but not full-text indexing, while > MyISAM supports full-text indexing but not foreign-key constraints. InnoDB does support full-text search since MySQL 5.6

Re: Implementing Full Text Search in Django --Ticket #3254

2013-03-21 Thread Luke Sneeringer
On Mar 21, 2013, at 7:00 PM, Russell Keith-Magee 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

Implementing Full Text Search in Django --Ticket #3254

2013-03-21 Thread Bharadwaj Desikan
Hi Guys, I would like to Contribute Towards Implementing Full Text Search in the Django and have seen the following ticket https://code.djangoproject.com/ticket/3254#no1 If someone can throw some light on What is Expected on the Postgre side .. I would like to give a shot to Index for