Re: [GENERAL] Design Table & Search Question

2007-05-31 Thread Joshua D. Drake
Ian Harding wrote: On 5/31/07, Joshua D. Drake <[EMAIL PROTECTED]> wrote: Ian Harding wrote: > tsearch indexes have to reside in the table where the data is, for the > automagical functions that come with it to work. You can define a > view that joins the tables, then search each of the index c

Re: [GENERAL] Design Table & Search Question

2007-05-31 Thread Ian Harding
On 5/31/07, Joshua D. Drake <[EMAIL PROTECTED]> wrote: Ian Harding wrote: > tsearch indexes have to reside in the table where the data is, for the > automagical functions that come with it to work. You can define a > view that joins the tables, then search each of the index columns for > the val

Re: [GENERAL] Design Table & Search Question

2007-05-31 Thread Joshua D. Drake
Ian Harding wrote: tsearch indexes have to reside in the table where the data is, for the automagical functions that come with it to work. You can define a view that joins the tables, then search each of the index columns for the values you are looking for. No they don't. Joshua D. Drake

Re: [GENERAL] Design Table & Search Question

2007-05-31 Thread Ian Harding
tsearch indexes have to reside in the table where the data is, for the automagical functions that come with it to work. You can define a view that joins the tables, then search each of the index columns for the values you are looking for. In my experience, the LIKE searches are fast for relative

Re: [GENERAL] Design Table & Search Question

2007-05-31 Thread Gabriel Laet
Thank you, Michael! I'm looking some examples and doing tests to find the best search solution. Best, On 5/30/07, Michael Glaesemann <[EMAIL PROTECTED]> wrote: On May 30, 2007, at 13:59 , Gabriel Laet wrote: > I'm developing an application where basically I need to store cars. > Every car ha

Re: [GENERAL] Design Table & Search Question

2007-05-30 Thread Michael Glaesemann
On May 30, 2007, at 13:59 , Gabriel Laet wrote: I'm developing an application where basically I need to store cars. Every car has a Make and Model association. Right now, I have three tables: MAKE, MODEL (make_id) and CAR (model_id). 1) I'm not sure if I need or not to include "make_id" to the

[GENERAL] Design Table & Search Question

2007-05-30 Thread Gabriel Laet
Hi, I'm developing an application where basically I need to store cars. Every car has a Make and Model association. Right now, I have three tables: MAKE, MODEL (make_id) and CAR (model_id). 1) I'm not sure if I need or not to include "make_id" to the CAR table. To me, it's clear to associate just