I think your pretty much on target with the below. It is possible to work
around these issues on some level, but I can see how that might get unwieldly
in a hurry. While I won't tell you to "go code it if you need it", I might
ask that you consider what your paying in Oracle licenses and think
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Saturday, 10 January 2004 6:05 AM
> To: [EMAIL PROTECTED]
> Subject: [GENERAL] Hierarchical queries
>
>
> Hello everybody!
>
> Does someone know how to build hierarchical queries to the postgresql?
>
Th
Dear all,
i have a problem with insertion data and running post insert trigger
on it.
Preambula:
there is a table named raw:
ipsrc | cidr
ipdst | cidr
bytes | bigint
time | timestamp
Triggers:
daily_trigger AFTER INSERT OR UPDATE ON raw FOR EACH ROW EXECUTE PROCEDURE
daily_func()
and the
Thanks Joe,
But this function is not giving a path from one element to other, it
is just truncating the tree beginning from the start element, but it
is not rotating the whole tree making starting element a tree's root.
JC> See contrib/tablefunc for a function called connectby().
Regards,
Anton
Hi Amir Khawaja ,
I have a rather trivial (I hope) question about OID types and
PostgreSQL. Since PostgreSQL creates tables "WITH OIDS" by default,
I'm wondering if it is bad practice to allow the default behaviour.
For example, if I have a database with 60+ tables (all tables have
their own P
