PostgreSQL Reference Guide

On Mon, 23 Mar 1998, Thomas G. Lockhart wrote:
>> Seems that rules doesn't work.
>> There is an example how to create a rule to update a view on "man create view"
>>        --Specify deletion semantics for toyemp
>>        create rule example1 as
>>            on delete to toyemp
>>            do instead delete emp
>>            where emp.oid = current.oid
>>
>> Should I document CREATE RULE or ...?

>How about posting a question to the docs list _and_ to the hackers list
>saying you are writing docs on CREATE RULE and asking for a working
>example. There are one or two people who have been working on this
>recently, and they should be able to help.

You are rigth.  Please there's somebody that can HELPPPPPPPPPPP me ???

>> - Do you know what kind of privilege one may have on indexes or sequences ?

>Indices - none, since they are just optimizations for tables.
>Sequences - not sure. Ask on the lists?

>> btw, how is it going?
>>
>> - Very well. We have already the following 12 pages:

>Great! Are you writing with the SGML markup, or are we adding that
>later?

For now I'm writing it in text mode, later I, or someone else can convert
it to SGML. What do you think about ?

>> I have a few questions about some statements:
>>
>> * ABORT is the same as COMMIT.
>> * END   is the same as ROLLBACK.

>No, the opposite:
>ABORT == ROLLBACK
>END == COMMIT

Yes. I know.

>>   I suppose that ABORT and END are both deprecated feature and I'm thinking
>>     to skip this pages.

>Hmmm. It does raise the question: where should they go? I'm guessing
>that they are holdovers from the PostQuel language, but don't know for
>sure. We should either document them or remove them from the parser.

>How about writing a doc page for them, but basically _only_ show syntax
>and then say that they are equivalent to, for example, ROLLBACK, and
>refer to that doc for more info?

                          - Tom