From: | Ray O'Donnell <ray(at)rodonnell(dot)ie> |
---|---|
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:38:14 |
Message-ID: | 7d2c5ed8-ad27-611e-7717-f3c5e3aa4995@rodonnell.ie |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 29/08/2021 17:36, ourdiaspora wrote:
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>
> On Sunday, August 29th, 2021 at 5:24 PM, Adrian Klaver
> <adrian(dot)klaver(at)aklaver(dot)com> wrote:
>
>>
>> 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.
>
> 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?
I'd save a timestamp with the session data, and then run a cron job
which deletes sessions older than whatever lifetime you want.
Ray.
--
Raymond O'Donnell // Galway // Ireland
ray(at)rodonnell(dot)ie
From | Date | Subject | |
---|---|---|---|
Next Message | ourdiaspora | 2021-08-29 16:38:31 | Re: database design with temporary tables |
Previous Message | ourdiaspora | 2021-08-29 16:36:25 | Re: database design with temporary tables |