Re: [GENERAL] Database design for separate tsearch table

2008-10-23 Thread Ivan Sergio Borgonovo
On Thu, 23 Oct 2008 14:20:49 +0200 Mikkel Høgh <[EMAIL PROTECTED]> wrote: > >but it seem that just searching on a tsvector in maintable > >build up with > > > >setweight(to_tsvector('pg_catalog.english', > >coalesce(maintable.body,'')), 'A') || ' ' || > > > >setweight(to_tsvector('pg_catalog.engli

Re: [GENERAL] Database design for separate tsearch table

2008-10-23 Thread Mikkel H??gh
On Thu, Oct 23, 2008 at 01:06:26AM +0200, Ivan Sergio Borgonovo wrote: weight them and you'll be able to search by field and "globally". I didn't make any scientific test but I previously had something like: create table subtable ( subtableid int, body text, ftidx tsvector ) create table mai

Re: [GENERAL] Database design for separate tsearch table

2008-10-22 Thread Ivan Sergio Borgonovo
On Thu, 23 Oct 2008 00:10:19 +0200 Mikkel Høgh <[EMAIL PROTECTED]> wrote: > Hi, > I'm trying to make a module allowing Drupal to take advantage of > PostgreSQL's excellent Full Text Search, aka. tsearch. > Since this module will probably not become part of Drupal core > right off the bat, I need

[GENERAL] Database design for separate tsearch table

2008-10-22 Thread Mikkel H??gh
Hi, I'm trying to make a module allowing Drupal to take advantage of PostgreSQL's excellent Full Text Search, aka. tsearch. Since this module will probably not become part of Drupal core right off the bat, I need to do this without modifying Drupal's own tables, so I've created a new one for the