Re: database design with temporary tables - Mailing list pgsql-general

From Adrian Klaver
Subject Re: database design with temporary tables
Date
Msg-id 918c3f8f-cd38-aace-5e6d-7a67a764648e@aklaver.com
Whole thread Raw
In response to Re: database design with temporary tables  (ourdiaspora <ourdiaspora@protonmail.com>)
List pgsql-general
On 8/29/21 9:36 AM, ourdiaspora wrote:
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> 
> On Sunday, August 29th, 2021 at 5:24 PM, Adrian Klaver <adrian.klaver@aklaver.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
maximumtime (such as 24 hours), even up to a certain time if the web browser crashes for example?
 

This is a it depends answer. Some factors in play:

1) Number of users over say a 24 hour period.

2) The size of the CSV files.

3) Is the data merge a one time thing or can it be repeated in a time 
period.

4) Are users going to be repeat customers?

For this sort of thing I write out a detailed outline of the 
who/what/why/where/when. In doing that answers tend to follow.

> 
>>
>> The abo
>>
> 
> Incomplete response?
> 
> 
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com



pgsql-general by date:

Previous
From: ourdiaspora
Date:
Subject: Re: database design with temporary tables
Next
From: Adrian Klaver
Date:
Subject: Re: database design with temporary tables