On April 2, 2015, Scott Ribe wrote:
> On Apr 2, 2015, at 10:14 PM, Adrian Klaver wrote:
> > EXECUTE 'insert into ' || quote_ident(tblname) || ' values(' || new.* ||
> > ')'
>
> Not that easy, strings are not quoted correctly, and null values are blank.
> Might be a function to translate new.* into
> I imagine the configuration was mangled somewhere down the line.
> Perhaps I need to reinstall Ubuntu, though it's not something I look
> forward to (I already tried uninstalling Postgres and wiping away all
> references to it prior to my last install).
>
> Thanks for taking a look!
>
> -
On Thursday 26 January 2006 19:24, Rich Shepard wrote:
> On Thu, 26 Jan 2006, Stephan Szabo wrote:
> > Did you put a semicolon at the end of the command? I get a
> > ERROR: syntax error at or near "username" at character 26
> > LINE 1: create database contacts username=sszabo
>
> Stephan,
>
>
> You could write a one trigger for the table to handle both.
>
Something like this :
-
CREATE OR REPLACE FUNCTION multi_tsearch2() RETURNS TRIGGER AS '
DECLARE
BEGIN
NEW.fti_title = to_tsvector(''default'', NEW.title);
NEW.fti_author_list = to_tsvector(''simple'', NEW.author_list);
>
> The configuration seems to work fine, but I can't get tsearch2 to
> use the 'author' config for column 'author_list' and 'default'
> config for column 'title'. Is there any way to accomplish this?
>
It's totally possible. I don't think you can accomplish this using the simple
tsearch trigger
> > A & (B | (New OperatorTheNextWordMustFollow York))
>
I had thought about this before myself. Alas I have never had the time to
properly investigate implementing such a feature.
:(
A & (B | (New + York))
Something like that?
> Actually, I love that idea. Oleg, would it be possible to c
On Wednesday 23 November 2005 06:55, Rick Schumeyer wrote:
> I apologize if I'm being dense, but I'm not completely following the
> explanation. It is true that my pg_ts_cfg.locale is set to en_US.UTF-8.
>
> It was my understanding that specifying "default" as in
>
That takes the locale that is s
On Tuesday 22 November 2005 21:45, Rick Schumeyer wrote:
> Is there something in tsearch2 that prevents more than one index per table?
>
> I would like an index on field A, and a separate index on field B.
>
> The index builds fine for A, but gives an error for B. The error text is
>
>
>
> ERROR:
On Saturday 24 September 2005 00:09, Oleg Bartunov wrote:
> Ron,
>
> probably you need to write custom parser. tsearch2 supports
> different parsers.
>
To expand somewhat on what Oleg mentioned, you can find a howto on writing a
custom parser here :
http://www.sai.msu.su/~megera/postgres/gist/ts
On Saturday 13 August 2005 16:10, CSN wrote:
> Greetings-
>
> How can I remove tsearch2 (all its tables, types,
> functions, etc.) from a database?
>
Wherever the contrib files are installed (where tsearch2.sql is), there should
also be an untsearch2.sql file. Just run that on the database.
And
> It seems to be selective of only numbers, words with numbers in them,
> words with '.' or '/' characters. It completely ignores any other words
> or text in any of the 3 fields.
>
This is a very big hint to your problem.
> You requested the pg_ts_* tables:
> On the Linux-redhat, pg7.3.2
>
> pg
11 matches
Mail list logo
