API methods for removing worlds and games

nik commented

2017-03-20 11:43:26 +01:00

(Migrated from edugit.org)

No description provided.

nik commented

2017-05-09 17:01:05 +02:00

(Migrated from edugit.org)

First, add a column named enabled to Game. Add an on_update trigger, which will ensure that if a game is disabled, all worlds related to it are disabled, too (look into SQLAlchemy docs for how to add on_update triggers).

Add an API method (a method following the structure of our API methods, decorated as api_method) to World, which will delete the world and all objects related to it, but only if the world was disabled before. Also add an API method to Game, which deletes the game if it is disabled, and cascades to the delete methods of all associated worlds.

First, add a column named enabled to Game. Add an on_update trigger, which will ensure that if a game is disabled, all worlds related to it are disabled, too (look into SQLAlchemy docs for how to add on_update triggers). Add an API method (a method following the structure of our API methods, decorated as api_method) to World, which will delete the world *and all objects related to it*, but only if the world was disabled before. Also add an API method to Game, which deletes the game if it is disabled, and cascades to the delete methods of all associated worlds.

nik commented

2017-05-09 17:01:10 +02:00

(Migrated from edugit.org)

Reassigned to @eike

nik commented

2017-05-09 17:17:38 +02:00

(Migrated from edugit.org)

Also, in the code scanning available games, add a reverse scan that looks for objects in the game table, disabling all games that are not available anymore.

eike commented

2017-05-09 17:54:23 +02:00

(Migrated from edugit.org)

Mentioned in commit 1625ef3038

Mentioned in commit 1625ef3038b53f42a214f09cf21e8c5908740d2a

eike commented

2017-05-09 17:54:23 +02:00

(Migrated from edugit.org)

Mentioned in commit f62edf7f2c

Mentioned in commit f62edf7f2c3055d206847a658b5687d73b1101e4

eike commented

2017-05-09 18:21:53 +02:00