[GENERAL] varchar(n) VS text

Having read http://www.postgresql.org/docs/8.2/interactive/datatype-character.html I am puzzling over this issue: 1) Is there ever ANY reason to prefer "varchar(n)" to "text" as a column type? 2) For instance, if I know that a character-type column will never contain more than 300 characters, w

[GENERAL] 8.3: where's the replacement tsearch2 module?

I just downloaded the 8.3 Windows installation (binary with installer). My database uses tsearch2. I was about to follow the conversions instructions found at Appendix F31 (on the new tsearch module). http://www.postgresql.org/docs/8.3/static/tsearch2.html However, I hit a problem when I get to

Re: [GENERAL] 8.3: where's the replacement tsearch2 module?

> > My database uses tsearch2. I was about to follow the conversions > > instructions found at Appendix F31 (on the new tsearch module). > > http://www.postgresql.org/docs/8.3/static/tsearch2.html > The docs will need to be updated because tsearch2 is now in the core and > should already be availa

[GENERAL] tsearch strategy for incremental search

I am trying to implement an incremental search engine. The service should start searching when the user has typed at least 3 characters. I am thinking of using the following strategy: a) Create a function string_to_three_char_tsvector(str text) that would generate the tsvector composed of the thr

Re: [GENERAL] tsearch strategy for incremental search

2008/6/30 Oleg Bartunov <[EMAIL PROTECTED]>: > tsearch will have prefix search support in 8.4. Thanks Oleg! That's fantastic news! In the meantime, carrying on with my earlier idea, here's the little function I came up with for extracting the 3-char-lexeme tsvector, in case anyone's interested:

Re: [GENERAL] tsearch strategy for incremental search

2008/6/30 Oleg Bartunov <[EMAIL PROTECTED]>: > you, probably, can use custom configuration, which uses pg_3chars > dictionary. Thanks Oleg. That sounds like a cleverer (and more natural) idea than mine. I am intrigued: is "pg_3chars" something that's part of the current distribution of postgres

[GENERAL] Getting several columns from subselect with LIMIT 1

I have a PERSONS table. I also have a PROGENY table, which is a many-to-many association table with two foreign keys to the PERSONS table to itself. (In this day and age, not only can an individual have any number of children, but also a person can have any number of parents! At least, let's assum

Fwd: [GENERAL] Getting several columns from subselect with LIMIT 1

Thanks for the suggestion. Unfortunately I get an INVALID COLUMN REFERENCE (SQL state: 42P10) to the effect that the subselect in the FROM clause cannot reference other tables at the same request level. 2008/9/20 Marcus Engene <[EMAIL PROTECTED]>: >> >> SELECT >>persons.*, >>( >>

[GENERAL] tsearch2, locale, UTF-8 and Windows

Over the past few days, I have been reading everything I could about tsearch2, but I cannot figure out what the latest status is concerning the "default locale" on a Windows UTF-8 database under PostgreSQL 8.2. More specifically, I have a UTF-8 database containing information in five different Eu

Re: [GENERAL] tsearch2, locale, UTF-8 and Windows

ges (see quoted post below), I don't know on what factor to base my choice of initdb locale. Suggestions? On Jan 28, 3:28 am, [EMAIL PROTECTED] ("Pierre Thibaudeau") wrote: [...] I cannot figure out what the latest status is concerning the "default locale" on a Windows UTF-8

[GENERAL] convert(USING utf8_to_iso_8859_15) on Windows

Is this a documented phenomenon with the "convert" function? The first result is what's expected: SELECT convert('Gregoire' USING utf8_to_iso_8859_15); "Gregoire" But I don't understand the next result, when I put an acute accent over the first "e": SELECT convert('Grégoire' USING utf8_to_iso_

Fwd: [GENERAL] convert(USING utf8_to_iso_8859_15) on Windows

rks with UTF8, via the ODBC driver. Say again that I output the data with another software that expects UTF8, via the JDBC driver. Why does it matter that my system should be localized in another encoding? 2007/1/29, Tom Lane <[EMAIL PROTECTED]>: "Pierre Thibaudeau" <[EMAIL

[GENERAL] "simple" dict with stop words in tsearch2

In tsearch2, I would like to use the "simple" dictionary along with my own list of stopwords. In other words, once the text is parsed into tokens, no stemming whatsoever, but stopwords are removed. Is there an easy way to produce that result, using the standard "simple" dictionary?

Re: [GENERAL] "simple" dict with stop words in tsearch2

Brilliant! Thank you! > In tsearch2, I would like to use the "simple" dictionary along with my > own list of stopwords. > [...] sure, just specify dict_initoption. For example, test=# update pg_ts_dict set dict_initoption='contrib/english.stop' where dict_name='simple'; UPDATE 1 test=# selec