Re: user constructed where clause - Mailing list pgsql-general

From Yelai, Ramkumar IN BLR STS
Subject Re: user constructed where clause
Date
Msg-id 8D15F77F211D7D4786182E1C8E679FAD2C72B02B03@INBLRK77M1MSX.in002.siemens.net
Whole thread Raw
In response to Re: user constructed where clause  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-general

Thanks  David for the nice suggestion.

 

Text search would not my requirement. Because user wants to provide condition similar to where clause. 

 

I thought let postgres query the data based on only time column. That result would be stored in cursor and fetch 5000 sequentially when the user ask. Once after the result is received by UI, let UI  do the complete query processing.

 

I am not sure about this idea, but is that possible I can apply where clause on cursor result (in 5000 batch)?

 

Thanks & Regards,

Ramkumar.

 

From: David G. Johnston [mailto:david.g.johnston@gmail.com]
Sent: Wednesday, June 10, 2015 1:48 AM
To: Yelai, Ramkumar IN BLR STS
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] user constructed where clause

 

On Tue, Jun 9, 2015 at 4:48 AM, Yelai, Ramkumar IN BLR STS <ramkumar.yelai@siemens.com> wrote:

Now, the requirement is if user provides filter information based on every column from the web UI, this filter will let the user construct the “where clause” and provide to postgresql.

In a month this table exceeds millions of record. If  I use the user-constructed query then it would take lot of time as the user may not include indexed column in the user-constructed query.

 

​The first solution that comes to mind is to construct a document containing the relevant information, index that, and then provide a single search input field that is used to construct a text search query that you apply against the indexed document.

 

In short, forget the fact that there are fields and just index and search the content.

 

Add additional controls to the UI for just those fields that are indexed.

 

David J.

 

pgsql-general by date:

Previous
From: Keith Rarick
Date:
Subject: Re: Alter column from text[] to uuid[]
Next
From: Tom Lane
Date:
Subject: Re: support for ltree