Date: Tue, 13 Dec 2022 18:54:25 +0100
From: Jiri Vlasak <jiri.hubacek@gmail.com>
To: siiky <github-siiky@net-c.cat>
Cc: ~qeef/damn-project@lists.sr.ht
Subject: Re: SQLite as DB alternative
Message-ID: <Y5i8UQLaHmpKQ7Lx@gmail.com>
References: <bd4eeb77-f669-9aa4-8e20-58e67003bb22@net-c.cat>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <bd4eeb77-f669-9aa4-8e20-58e67003bb22@net-c.cat>

Hello and sorry for late reply.

> When developing damn did you consider SQLite? If yes, why did you end
> up choosing Postgres?

First, the damn-server depends on PostGIS extension [1]. Second, it is
designed for greater loads because of mapathon use-case.

> If not, do you think deploying with SQLite instead of Postgres is
> feasible?

I do not think so. damn-server is "just API to the database" -- based on
requests over HTTP, damn-server decides which SQL query to run. A lot
can be done by just queries, see for example st_divide function [2] and
its use when saving the area [3].

Please, note small inconsistency that is going to be solved as part of
https://todo.sr.ht/~qeef/damn-project/7 hopefully this year yet. In the
README of the damn-server, it is mentioned that it is possible to run
the docker image with the PostGIS database from the damn-deploy [4].
However, along with the steps in the README, to sucessfully build the
damndb docker image, the content of the damndb/Dockerfile needs to be
changed to:

	FROM postgis/postgis:11-3.3-alpine

	ENV POSTGRES_PASSWORD ${POSTGRES_PASSWORD:-pass}
	ENV POSTGRES_USER ${POSTGRES_USER:-damnuser}
	ENV POSTGRES_DB ${POSTGRES_DB:-damndb}

	ADD --chown=postgres https://git.sr.ht/~qeef/damn-server/blob/master/20_create_damn_db.sql /docker-entrypoint-initdb.d/

[1]: https://postgis.net/
[2]: https://git.sr.ht/~qeef/damn-server/tree/master/item/20_create_damn_db.sql
[3]: https://git.sr.ht/~qeef/damn-server/tree/master/item/damn_server/area.py#L158
[4]: https://git.sr.ht/~qeef/damn-deploy