| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | ourdiaspora <ourdiaspora(at)protonmail(dot)com> |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: database design with temporary tables |
| Date: | 2021-08-29 16:53:43 |
| Message-ID: | 73de336d-b5d6-03e0-06e9-7754f4d1eb6e@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 8/29/21 9:38 AM, ourdiaspora wrote:
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>
> On Sunday, August 29th, 2021 at 5:30 PM, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> wrote:
>
>> On 8/29/21 9:24 AM, Adrian Klaver wrote:
>>
>>
>> Whoops, unfinished thought. What I was going to ask is:
>>
>> The above is not clear to me. Are you asking about the Postgres
>>
>> documentation?
>>
>
> Yes, wanted to know relevant parts because often the first problem is to know which part of the (extensive) documentation to read...
>
From what I see it is basic operations; CREATE TABLE, SELECT, INSERT,
UPDATE and COPY.
As I said in my previous post create a fairly detailed design flow first
and from that you will see what operations you need to do and what part
of the docs you need to look at.
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ray O'Donnell | 2021-08-29 16:56:53 | Re: database design with temporary tables |
| Previous Message | Adrian Klaver | 2021-08-29 16:50:15 | Re: database design with temporary tables |