| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Дмитрий Иванов <firstdismay(at)gmail(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Two academic questions |
| Date: | 2022-02-02 06:36:49 |
| Message-ID: | CAKFQuwYx471oGV8_Mn-W0WbTG_61w03-fHYH0zP7HMorTPNQcA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tuesday, February 1, 2022, Дмитрий Иванов <firstdismay(at)gmail(dot)com> wrote:
>
>>>
>>> DEFAULT VALUE <> GENERATED ALWAYS AS STORED
>>> the DEFAULT value is not recalculated when the reference column are
>>> changed. is not an identical construction GENERATED ALWAYS AS STORED
>>>
>>> *reply:*
>>> They are in a separate list “Methods”.
>>> This approach was used for other databases *long before* generated
>>> columns were implemented in PostgreSQL.
>>> ====================
>>>
>>>
>> It has to do with the syntax of generated and that you can generate data
>> in different ways. Calling those ways “methods” seems reasonable.
>>
>> It's hard to argue with that. However, it is not quite clear to me, what
> origin are we talking about? I have worked with MS products and currently
> with PostgreSQL and have not encountered this interpretation.
>
“Origin”? The documentation, and my internalizing of it based on my
personal experiences.
Anyway, I did my best given the unclear (to me at least) and limited
information you provided, and the fact I don’t really understand the
question.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Дмитрий Иванов | 2022-02-02 07:12:24 | Re: Two academic questions |
| Previous Message | Дмитрий Иванов | 2022-02-02 06:12:51 | Re: Two academic questions |