installation:
make && make install
upgrade issue is tricky. their is a lower burden of backwards
compatibility than on in-core features. for example, some of contrib
was gpl and is getting moved out/changed. however, the more popular
modules, like tsearch are very well supported. I haven't us
On 10/11/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> I think you should have a look at the ltree contrib package. It
> implements tree-like structures, and probably makes your problem much
> simpler.
I have never used contrib modules with PostgreSQL - are they easy to
handle - I mean, esp
I think you should have a look at the ltree contrib package. It
implements tree-like structures, and probably makes your problem much
simpler.
I have never used contrib modules with PostgreSQL - are they easy to
handle - I mean, especially upon upgrade, etc.
---(end o
[EMAIL PROTECTED] wrote:
I am writing a plpgsql (PostgreSQL 8.x) trigger function that should do
something on a number of records. The records are in a very simple table
with two columns - 'parent_id' and 'child_id'. A 'child' can be as well
a 'parent' to one or more children - in this case its
Merlin Moncure wrote:
> it's not exactly clear if you are asking about handling children
> recursively or not (meaning, you have to find the children's children,
> and so on). If so, I'd suggest taking a look here:
>
http://people.planetpostgresql.org/merlin/index.php?/archives/2-Dealing-With-Re
On 10/9/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
I am writing a plpgsql (PostgreSQL 8.x) trigger function that should do
something on a number of records. The records are in a very simple table
with two columns - 'parent_id' and 'child_id'. A 'child' can be as well
a 'parent' to one or mo
I am writing a plpgsql (PostgreSQL 8.x) trigger function that should do
something on a number of records. The records are in a very simple table
with two columns - 'parent_id' and 'child_id'. A 'child' can be as well
a 'parent' to one or more children - in this case its ID appears as many
times
