On Thu, Feb 24, 2011 at 1:10 AM, Michael Glaesemann wrote:
>
> On Feb 23, 2011, at 13:49, John R Pierce wrote:
>
> > On 02/23/11 4:44 AM, Stephane Bortzmeyer wrote:
> >>> *3. Start-End IP format :* 1.2.3.0-1.2.3.255
> >> You don't even need to program the conversion, it is already done:
> >>
On Thu, Feb 24, 2011 at 3:03 AM, Tom Lane wrote:
> John R Pierce writes:
> > On 02/23/11 4:44 AM, Stephane Bortzmeyer wrote:
> > *3. Start-End IP format :* 1.2.3.0-1.2.3.255
> >> You don't even need to program the conversion, it is already done:
> >>
> >> % netmask 1.2.3.0:1.2.3.255
> >> 1.
Hi All,
I wanted to store ip addresses in table. I wanted to support the following 3
types of ip addresses.
*1. Wildcard format :* 1.2.3.*
*
*
*2. CIDR format:* 1.2.3/24 OR 1.2.3.4/255.255.255.0
*
*
*3. Start-End IP format :* 1.2.3.0-1.2.3.255
I had a look at CIDR
attery && magnetic induction) | (database management system)'
*Here i need not to mention the & operator between *portable, battery.
*Is there any way we can specify this in PostgreSQL Fulltext search (i.e
without bothering about inserting & operator in between)?
Thanks,
Gaini Rajeshwar
Hi All,
I am doing a fulltext search something like this:
SELECT doc_id FROM docs WHERE tsv_title($$'magnetic induction'$$) OR
tsv_body($$'magnetic induction'$$) OR tsv_abstract($$'abstract'$$)
It is taking approximately 100 secs to execute.
But running the query on individual column something
s case it is working very well,
but in the
earlier case.
Can any of you tell me how to do in the case of non-character data type like
doc_id?
Thanks,
Gaini Rajeshwar*
*
On Mon, Oct 12, 2009 at 8:02 PM, Ivan Sergio Borgonovo wrote:
> On Mon, 12 Oct 2009 19:26:55 +0530
> Gaini Rajeshwar wrote:
>
> > Ivan,
> > If i create a tsvector as you mentioned with concatenation
> > operator, my search query will search in any of these fields wh
On Tue, Oct 13, 2009 at 11:00 AM, Christophe Pettus wrote:
>
> On Oct 12, 2009, at 9:59 PM, Gaini Rajeshwar wrote:
>
>> From the readings and documentation, i understood that there are 4 weights
>> A,B,C,D (1.0, 0.4, 0.2, 0.1 are the defalut values, which can be changed)
Hi,
>From the readings and documentation, i understood that there are 4 weights *
A,B,C,D *(*1.0, 0.4, 0.2, 0.1* are the defalut values, which can be changed)
to rank the search results.
But using just these 4 weights is too less to rank the search results, as i
have many fields to use for ranking.
On Mon, Oct 12, 2009 at 7:26 PM, Ivan Sergio Borgonovo wrote:
> On Mon, 12 Oct 2009 19:11:01 +0530
> Gaini Rajeshwar wrote:
>
> > I think you misunderstood my question. let me give clear idea
> > about what i need.
> >
> > I am using PostgreSQL full
7:16 PM, Ivan Sergio Borgonovo wrote:
> On Mon, 12 Oct 2009 18:46:02 +0530
> Gaini Rajeshwar wrote:
>
> > Hi,
> > is there a way to rank the search results based on multiple fields
> > in postgreSQL?
> > For example,
> > i have *title*, *abstract*, *summary*,
y around to do this?
On Mon, Oct 12, 2009 at 6:53 PM, Raymond O'Donnell wrote:
> On 12/10/2009 14:16, Gaini Rajeshwar wrote:
> > Hi,
> > is there a way to rank the search results based on multiple fields in
> > postgreSQL?
> > For example,
> > i have *title*,
Hi,
is there a way to rank the search results based on multiple fields in
postgreSQL?
For example,
i have *title*, *abstract*, *summary*, *body* as fields/columns in my
database. When user searches on *title*, i want to rank the results based on
*title* field as well as *summary* field, where impor
13 matches
Mail list logo
