pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feedUpdate needed for documentation
3+ messages / 2 participants
[nested] [flat]
* Update needed for documentation
@ 2001-05-11 07:41 Justin Clift <justin@postgresql.org>
2001-06-04 19:32 ` Re: Update needed for documentation Bruce Momjian <pgman@candle.pha.pa.us>
0 siblings, 1 reply; 3+ messages in thread
From: Justin Clift @ 2001-05-11 07:41 UTC (permalink / raw)
To: pgsql-docs
Hi all,
Spotted the following line in the 7.1 Interactive docs, not sure if it's
been updated :
"As of the current release (v7.0), STATEMENT triggers are not
implemented."
It's in the PostgreSQL Doc page which explains "CREATE TRIGGER".
Regards and best wishes,
Justin Clift
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Update needed for documentation
2001-05-11 07:41 Update needed for documentation Justin Clift <justin@postgresql.org>
@ 2001-06-04 19:32 ` Bruce Momjian <pgman@candle.pha.pa.us>
0 siblings, 0 replies; 3+ messages in thread
From: Bruce Momjian @ 2001-06-04 19:32 UTC (permalink / raw)
To: Justin Clift <justin@postgresql.org>; +Cc: pgsql-docs
> Hi all,
>
> Spotted the following line in the 7.1 Interactive docs, not sure if it's
> been updated :
>
> "As of the current release (v7.0), STATEMENT triggers are not
> implemented."
>
> It's in the PostgreSQL Doc page which explains "CREATE TRIGGER".
I see in command/trigger.c:
if (stmt->row)
TRIGGER_SETT_ROW(tgtype);
else
elog(ERROR, "CreateTrigger: STATEMENT triggers are unimplemented, yet");
We have per-row triggers but not per-statement triggers. Seems we use
RULEs for those.
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Update needed for documentation
@ 2001-06-10 03:47 Bruce Momjian <pgman@candle.pha.pa.us>
0 siblings, 0 replies; 3+ messages in thread
From: Bruce Momjian @ 2001-06-10 03:47 UTC (permalink / raw)
To: Justin Clift <aa2@bigpond.net.au>; +Cc: pgsql-docs
I understand now, and you are correct. There is no reason to mention
the release version in the docs, in most cases. Attached patch applied.
Thanks.
> Hi Bruce,
>
> My point was to get the documentation updated, not anything else. Probably
> we should bump the statement in the doc's to say "7.1.2".
>
> :-)
>
> Regards and best wishes,
>
> Justin Clift
>
> On Tuesday 05 June 2001 05:32, you wrote:
> > > Hi all,
> > >
> > > Spotted the following line in the 7.1 Interactive docs, not sure if it's
> > > been updated :
> > >
> > > "As of the current release (v7.0), STATEMENT triggers are not
> > > implemented."
> > >
> > > It's in the PostgreSQL Doc page which explains "CREATE TRIGGER".
> >
> > I see in command/trigger.c:
> >
> > if (stmt->row)
> > TRIGGER_SETT_ROW(tgtype);
> > else
> > elog(ERROR, "CreateTrigger: STATEMENT triggers are unimplemented,
> > yet");
> >
> > We have per-row triggers but not per-statement triggers. Seems we use
> > RULEs for those.
>
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
Attachments:
/bjm/diff (text/plain, 3.8K) download
Index: doc/src/sgml/ref/create_trigger.sgml
===================================================================
RCS file: /home/projects/pgsql/cvsroot/pgsql/doc/src/sgml/ref/create_trigger.sgml,v
retrieving revision 1.13
diff -c -r1.13 create_trigger.sgml
*** doc/src/sgml/ref/create_trigger.sgml 2001/05/27 09:59:28 1.13
--- doc/src/sgml/ref/create_trigger.sgml 2001/06/10 03:44:14
***************
*** 150,156 ****
Only the relation owner may create a trigger on this relation.
</para>
<para>
! As of the current release (v7.0), STATEMENT triggers are not implemented.
</para>
<para>
Refer to <command>DROP TRIGGER</command> for information on how to
--- 150,156 ----
Only the relation owner may create a trigger on this relation.
</para>
<para>
! As of the current release, STATEMENT triggers are not implemented.
</para>
<para>
Refer to <command>DROP TRIGGER</command> for information on how to
Index: doc/src/sgml/ref/psql-ref.sgml
===================================================================
RCS file: /home/projects/pgsql/cvsroot/pgsql/doc/src/sgml/ref/psql-ref.sgml,v
retrieving revision 1.55
diff -c -r1.55 psql-ref.sgml
*** doc/src/sgml/ref/psql-ref.sgml 2001/05/28 04:27:17 1.55
--- doc/src/sgml/ref/psql-ref.sgml 2001/06/10 03:44:16
***************
*** 1051,1057 ****
<note>
<para>
! As of <application>psql</application> version 7.0 it is no longer
necessary to save the command history, since that will be done
automatically on program termination. The history is
also loaded automatically every time <application>psql</application>
--- 1051,1057 ----
<note>
<para>
! In the current version, it is no longer
necessary to save the command history, since that will be done
automatically on program termination. The history is
also loaded automatically every time <application>psql</application>
***************
*** 1579,1585 ****
</para>
<para>
! As of version 7.0, <application>psql</application> automatically issues a
password prompt whenever the backend requests password authentication.
Because this is currently based on a hack, the automatic
recognition might mysteriously fail, hence this option to force a prompt.
--- 1579,1585 ----
</para>
<para>
! In the current version, <application>psql</application> automatically issues a
password prompt whenever the backend requests password authentication.
Because this is currently based on a hack, the automatic
recognition might mysteriously fail, hence this option to force a prompt.
Index: doc/src/sgml/ref/select.sgml
===================================================================
RCS file: /home/projects/pgsql/cvsroot/pgsql/doc/src/sgml/ref/select.sgml,v
retrieving revision 1.42
diff -c -r1.42 select.sgml
*** doc/src/sgml/ref/select.sgml 2001/05/30 04:32:30 1.42
--- doc/src/sgml/ref/select.sgml 2001/06/10 03:44:17
***************
*** 122,129 ****
table is scanned. If ONLY is not specified, the table and all its
descendant tables (if any) are scanned. * can be appended to the
table name to indicate that descendant tables are to be scanned,
! but as of <Productname>Postgres</Productname> 7.1 this is the default
! behavior. (In releases before 7.1, ONLY was the default behavior.)
</para>
</listitem>
</varlistentry>
--- 122,129 ----
table is scanned. If ONLY is not specified, the table and all its
descendant tables (if any) are scanned. * can be appended to the
table name to indicate that descendant tables are to be scanned,
! but in the current version, this is the default behavior.
! (In releases before 7.1, ONLY was the default behavior.)
</para>
</listitem>
</varlistentry>
/bjm/diff (text/plain, 3.8K) download
Index: doc/src/sgml/ref/create_trigger.sgml
===================================================================
RCS file: /home/projects/pgsql/cvsroot/pgsql/doc/src/sgml/ref/create_trigger.sgml,v
retrieving revision 1.13
diff -c -r1.13 create_trigger.sgml
*** doc/src/sgml/ref/create_trigger.sgml 2001/05/27 09:59:28 1.13
--- doc/src/sgml/ref/create_trigger.sgml 2001/06/10 03:44:14
***************
*** 150,156 ****
Only the relation owner may create a trigger on this relation.
</para>
<para>
! As of the current release (v7.0), STATEMENT triggers are not implemented.
</para>
<para>
Refer to <command>DROP TRIGGER</command> for information on how to
--- 150,156 ----
Only the relation owner may create a trigger on this relation.
</para>
<para>
! As of the current release, STATEMENT triggers are not implemented.
</para>
<para>
Refer to <command>DROP TRIGGER</command> for information on how to
Index: doc/src/sgml/ref/psql-ref.sgml
===================================================================
RCS file: /home/projects/pgsql/cvsroot/pgsql/doc/src/sgml/ref/psql-ref.sgml,v
retrieving revision 1.55
diff -c -r1.55 psql-ref.sgml
*** doc/src/sgml/ref/psql-ref.sgml 2001/05/28 04:27:17 1.55
--- doc/src/sgml/ref/psql-ref.sgml 2001/06/10 03:44:16
***************
*** 1051,1057 ****
<note>
<para>
! As of <application>psql</application> version 7.0 it is no longer
necessary to save the command history, since that will be done
automatically on program termination. The history is
also loaded automatically every time <application>psql</application>
--- 1051,1057 ----
<note>
<para>
! In the current version, it is no longer
necessary to save the command history, since that will be done
automatically on program termination. The history is
also loaded automatically every time <application>psql</application>
***************
*** 1579,1585 ****
</para>
<para>
! As of version 7.0, <application>psql</application> automatically issues a
password prompt whenever the backend requests password authentication.
Because this is currently based on a hack, the automatic
recognition might mysteriously fail, hence this option to force a prompt.
--- 1579,1585 ----
</para>
<para>
! In the current version, <application>psql</application> automatically issues a
password prompt whenever the backend requests password authentication.
Because this is currently based on a hack, the automatic
recognition might mysteriously fail, hence this option to force a prompt.
Index: doc/src/sgml/ref/select.sgml
===================================================================
RCS file: /home/projects/pgsql/cvsroot/pgsql/doc/src/sgml/ref/select.sgml,v
retrieving revision 1.42
diff -c -r1.42 select.sgml
*** doc/src/sgml/ref/select.sgml 2001/05/30 04:32:30 1.42
--- doc/src/sgml/ref/select.sgml 2001/06/10 03:44:17
***************
*** 122,129 ****
table is scanned. If ONLY is not specified, the table and all its
descendant tables (if any) are scanned. * can be appended to the
table name to indicate that descendant tables are to be scanned,
! but as of <Productname>Postgres</Productname> 7.1 this is the default
! behavior. (In releases before 7.1, ONLY was the default behavior.)
</para>
</listitem>
</varlistentry>
--- 122,129 ----
table is scanned. If ONLY is not specified, the table and all its
descendant tables (if any) are scanned. * can be appended to the
table name to indicate that descendant tables are to be scanned,
! but in the current version, this is the default behavior.
! (In releases before 7.1, ONLY was the default behavior.)
</para>
</listitem>
</varlistentry>
end of thread, other threads:[~2001-06-10 03:47 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2001-05-11 07:41 Update needed for documentation Justin Clift <justin@postgresql.org>
2001-06-04 19:32 ` Bruce Momjian <pgman@candle.pha.pa.us>
2001-06-10 03:47 Re: Update needed for documentation Bruce Momjian <pgman@candle.pha.pa.us>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox