| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "Ray O'Donnell" <ray(at)rodonnell(dot)ie> |
| Cc: | 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:48:22 |
| Message-ID: | CAKFQuwaJzvFf3jZ_nvyLtABZbP8habamJ_e9kKiUMu5304WbVA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sunday, August 29, 2021, Ray O'Donnell <ray(at)rodonnell(dot)ie> wrote:
>
>>>
>> Is there an alternative scenario, such as the user is able to create
>> a new table with saves the session data for a maximum time (such as
>> 24 hours), even up to a certain time if the web browser crashes for
>> example?
>
>
In general a database doesn’t change just because time has passed. You
will need to setup something external to the database schema if you want
time to cause change.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | ourdiaspora | 2021-08-29 16:49:29 | Re: database design with temporary tables |
| Previous Message | David G. Johnston | 2021-08-29 16:46:06 | Re: database design with temporary tables |