From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | ourdiaspora <ourdiaspora(at)protonmail(dot)com>, "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:24:41 |
Message-ID: | 0e9373c9-565c-5edb-5c71-b3ea40be9473@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 8/29/21 9:10 AM, ourdiaspora wrote:
> Readers,
>
> Some advice would be appreciated about appropriate tables to store temporary data.
>
> Scenario:
> User copies csv file of user data, presumably into some temporary table(s);
Presumably not. Temporary tables only live at most for the length of a
session. It would be a really bad idea to hold sessions open for 24
hours. That is assuming nothing else causes the session to drop and the
data to be lost.
> User selects data (read-only) from extant tables;
> Web server combines user data with read-only data to produce content visible to user as html and/or pdf document;
> User does not need to sign in to use web page, only the user e-mail address;
> User data deleted (including e-mail address) after time (e.g. 24 hours) and/or user selects to receive combined data via e-mail (after which all user data is automatically deleted).
>
> What part of the documention would be most relevant to read firstly, please?
The abo
>
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2021-08-29 16:30:08 | Re: database design with temporary tables |
Previous Message | ourdiaspora | 2021-08-29 16:10:34 | database design with temporary tables |