aboutsummaryrefslogtreecommitdiffstats
path: root/view/ru/invite.formal.subject.tpl
diff options
context:
space:
mode:
authorHarald Eilertsen <haraldei@anduin.net>2024-01-15 19:11:25 +0100
committerHarald Eilertsen <haraldei@anduin.net>2024-01-15 19:11:25 +0100
commitf71033b30dc20c67e6ed336178d1ac0144ea5c8a (patch)
tree52606b0b4027aba3174966d0b258316eee2b6df6 /view/ru/invite.formal.subject.tpl
parent885068834f8b4f5b0816075e95c55b31d0723511 (diff)
downloadvolse-hubzilla-f71033b30dc20c67e6ed336178d1ac0144ea5c8a.tar.gz
volse-hubzilla-f71033b30dc20c67e6ed336178d1ac0144ea5c8a.tar.bz2
volse-hubzilla-f71033b30dc20c67e6ed336178d1ac0144ea5c8a.zip
tests: Remove id from db fixtures.
It seems that PostgreSQL will not update the autoincrement index of the table when inserting rows with an id set. Later inserts without an id set will then fail, because they get assigned an id that already exists. MySQL seems to handle this just fine. Why the id column was added in the first place, one may wonder, but that's how it were. In any case, this broke the PostgreSQL tests in the gitlab CI environment. (While it mysteriously worked in my local ddev environment.) Anyways, the id column is not needed, and things work better without them.
Diffstat (limited to 'view/ru/invite.formal.subject.tpl')
0 files changed, 0 insertions, 0 deletions