| From: | Andreas Fromm <Andreas(dot)Fromm(at)physik(dot)uni-erlangen(dot)de> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: inserting via "on insert" rule |
| Date: | 2003-09-02 14:33:05 |
| Message-ID: | 3F54AA21.5060302@physik.uni-erlangen.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Peter Eisentraut wrote:
>Andreas Fromm writes:
>
>
>
>>I was thinking of defining a view "users" over "persons" which would let
>>me retrive the list of useres. But How would I implement the rule for
>>insertiung users? I tryed the following but NEW is not known where I
>>want to use it:
>>
>>CREATE VIEW users AS
>> SELECT * FROM persons WHERE is_user(person.id) = TRUE;
>>
>>CREATE RULE insert_on_users AS ON INSERT
>> TO users DO INSTEAD
>> INSERT INTO persons SELECT * FROM NEW;
>>
>>
>
>You can write
>
>... DO INSTEAD INSERT INTO persons VALUES (NEW.col1, NEW.col2, ...);
>
>
Yes, but what if I don't pass a certain col. Is the default value
inserted instead? Or will the transaction fail because of a wrong number
of columns?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-09-02 14:33:06 | Re: Commercial postgresql |
| Previous Message | Shridhar Daithankar | 2003-09-02 14:28:27 | Re: Commercial postgresql |