Fix performance problems in the database

[zner0L]

This is based on migrations from #15, which needs to be merged first.

I managed to significantly reduce the time required to SELECT by caching the state and changing it only on INSERT or UPDATE. On my local machine, a query like

SELECT Proceeding {*, initialAnalysis: {*}, secondAnalysis: {*}, app: {*}, uploads: {*}};

selecting all 18 Proceedings and all of their links takes 84 ms according to ANALYZE. The RAM requirements of the database also stay reasonable.

The custom migrations should also preserve the current state of the database.

[baltpeter]

This fixed it. thumbsup

[zner0L]

This is now properly rebased to main and ready to merge IMO. Do you still have something holding it up, @baltpeter?

[baltpeter]

Awesome.

[hgeet]

update