>> Additional Trigger Syntax (ie Oracle):
>I'm not seeing anything there more than syntactic sugar that PostgreSQL
>doesn't support, but no, it doesn't take that syntax.
Milla's syntax doesn't show that Oracle allows column level triggers.
That's the only difference I've noted. Column triggers are nice for
efficiency, e.g. the trigger doesn't fire when a column doesn't change. If
the trigger body is complex, you can test whether the OLD.col != NEW.col
for added efficiency in Postgres.
Rick
Martijn van Oosterhout
<kleptog@svana.org> To: Milla Erdee <millueradfa@yahoo.com>
Sent by: cc: pgsql-general@postgresql.org
pgsql-general-owner@pos Subject: Re: [GENERAL] Question regarding threaded mode
tgresql.org
02/14/2005 11:02 AM
Please respond to
Martijn van Oosterhout
On Fri, Feb 11, 2005 at 08:12:50PM -0500, Milla Erdee wrote:
> First, I appreciate PostgreSQL's extensive support for SQL and its
> feature set greatly, which is why I use it, because of its extensive and
> powerful features not found on some other SQL implementations and I hope
> that the capabilities of it will continue to be expanded and improved.
>
> Does PostGRESQL support or will it support a threaded server mode? Will
> such a mode be available on Unix-type systems?
Currently no. There's no real need for it so there's not really a push
for it either.
> Also, has PostgreSQL considered adding some CLOB and BLOB types?
Has had these for ages.
> Updating Views
You can create RULEs to do this.
> Triggers on Views
What would they do?
> Additional Trigger Syntax (ie Oracle):
I'm not seeing anything there more than syntactic sugar that PostgreSQL
doesn't support, but no, it doesn't take that syntax.
Hope this helps,
--
Martijn van Oosterhout <kleptog@svana.org> http://svana.org/kleptog/
> Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a
> tool for doing 5% of the work and then sitting around waiting for someone
> else to do the other 95% so you can sue them.
(See attached file: attl4bbc.dat)