Back then when I thought about the idea of using an SQL database instead of JSON, I would have planned to use a separate table for each application, where the include_vars are…
@reinhard I'm talking about these emails for the "logged" table. These emails do not need to be validated and are stored.
Thank you @reinhard
How about creating two tables? One for "logged" emails and one for "confirmed" emails. I assume that never confirmed emails are not usable and are kept for compliance?
Keeping the
.json
and the database together at the start may be preferable. This allows us to check that the behaviour is correct.At the same time, we can start migrating other…
Keeping the .json
and the database together at the start may be preferable. This allows us to check that the behaviour is correct.
At the same time, we can start migrating other components to…
It's as if I'd updated all the Pipenv.lock
files and this wasn't planned. Should I go back or is it OK?
@linus if I understand correctly, the REUSE API is not using PostgreSQL for development (https://git.fsfe.org/reuse/api/pulls/71/files#diff-a8af255e3836e7327821285b1659791a79535e7b). Should we do the same here?