Thread history

From Talk:LiteRumble
Viewing a history listing
Jump to navigation Jump to search
Time User Activity Comment
08:35, 19 November 2015 Frbod1 (talk | contribs) New reply created (Reply to Clear LiteRumble history)
08:14, 19 November 2015 Frbod1 (talk | contribs) New reply created (Reply to Clear LiteRumble history)
08:05, 19 November 2015 Skilgannon (talk | contribs) New reply created (Reply to Clear LiteRumble history)
07:54, 19 November 2015 Frbod1 (talk | contribs) New reply created (Reply to Clear LiteRumble history)
21:22, 18 November 2015 Skilgannon (talk | contribs) New reply created (Reply to Clear LiteRumble history)
15:05, 18 November 2015 Frbod1 (talk | contribs) New thread created  

Clear LiteRumble history

I have created my own LiteRumble instance running as a google app, as described in previous discussions. Now I want to know if it is possible to delete the battle history and the participated robots? I am experimenting with it since we want to have a roborumble event at our office and I want to delete my previous "testing" robots and matches and have a clean slate when we do the event.

Frbod1 (talk)15:05, 18 November 2015

You should be able to delete the data from the AppEngine web console. Otherwise you can simple make the clients upload to a different named rumble, and the old one can be for the demo/setup bots.

Skilgannon (talk)21:22, 18 November 2015

I have tried to remove the data from the datastore by selecting all database entries and delete them. But the data on the webpage is still there, so the data must be stored somewhere else. To create a new rumble seems like a annoying workaround :)

Frbod1 (talk)07:54, 19 November 2015

There may still be a copy in Memcache - if you clear Memcache and the datastore everything should be gone.

Skilgannon (talk)08:05, 19 November 2015

Haha, didn't reload the page before I submitted my last comment. I seem to have found the problem at the same time that you mentioned it. Thank you anyway!

Frbod1 (talk)08:35, 19 November 2015
 
 

Found the problem. Had to delete all database entries AND the memory cache.

Frbod1 (talk)08:14, 19 November 2015