From: | ourdiaspora <ourdiaspora(at)protonmail(dot)com> |
---|---|
To: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | database design with temporary tables |
Date: | 2021-08-29 16:10:34 |
Message-ID: | IRuoNkHXtafj7Vm_RhI-AB56qHPVRSDRD95NmX9lxlsQvmsK361slJ4ONjoP0GvX8tNsyXUD5KF1TW21uJyh15BDdrQCDHFDvPXa1Nu-eVE=@protonmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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);
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?
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2021-08-29 16:24:41 | Re: database design with temporary tables |
Previous Message | Tom Lane | 2021-08-29 13:51:58 | Re: Can we get rid of repeated queries from pg_dump? |