Re: database design with temporary tables

From: ourdiaspora <ourdiaspora(at)protonmail(dot)com>
To: Ray O'Donnell <ray(at)rodonnell(dot)ie>
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:49:29
Message-ID: uNTba3mLSehyXyCxXddUnxZL3Uq9tHzDTszFrQrdJlDvs9rwLffMhosaQv6LjIUbW2DiFptZ2optqdjC98tTWj4PamuThcALGtVU9woBDMU=@protonmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Sunday, August 29th, 2021 at 5:38 PM, Ray O'Donnell <ray(at)rodonnell(dot)ie> wrote:
>
> I'd save a timestamp with the session data, and then run a cron job
>
> which deletes sessions older than whatever lifetime you want.
>

Is it prudent in this scenario for the user to create (a) tables of her/his data, with role as her/his e-mail address (no password)?

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2021-08-29 16:50:15 Re: database design with temporary tables
Previous Message David G. Johnston 2021-08-29 16:48:22 Re: database design with temporary tables