Describe the bug
When you execute a drain it executes properly..however - the data stored cannot later be looked up because its missing `parent_id'
To Reproduce
Steps to reproduce the behavior:

1. Execute a drain
2. execute a lookup.

Expected behavior
lookup shows the drain event,
Screenshots

• If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem** via https://imgur.com/ or similar.

Server (please complete the following information):

• Prism Version: 2.1.7-SNAPSHOT
• Server Type: Spigot
• Server Version: 1.15.2

Additional context
[17:15:17] [Craft Scheduler Thread - 0/WARN]: [Prism] Plugin Prism v2.1.7-SNAPSHOT- generated an exception while executing task 1237
java.lang.NumberFormatException: null
at java.lang.Long.parseLong(Long.java:552) ~[?:1.8.0_181]
at java.lang.Long.parseLong(Long.java:631) ~[?:1.8.0_181]
at me.botsko.prism.actions.PrismRollbackAction.deserialize(PrismRollbackAction.java:35) ~[?:?]
at me.botsko.prism.database.sql.SqlSelectQueryBuilder.executeSelect(SqlSelectQueryBuilder.java:629) ~[?:?]
at me.botsko.prism.actionlibs.ActionsQuery.lookup(ActionsQuery.java:65) ~[?:?]
at me.botsko.prism.commands.LookupCommand.lambda$handle$0(LookupCommand.java:63) ~[?:?]
at org.bukkit.craftbukkit.v1_15_R1.scheduler.CraftTask.run(CraftTask.java:81) ~[spigot-1.15.2.jar:git-Spigot-2040c4c-1872231]
at org.bukkit.craftbukkit.v1_15_R1.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:54) [spigot-1.15.2.jar:git-Spigot-2040c4c-1872231]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_181]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_181]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_181]

This repository is no longer active. You can try to resubmit this at the current Prism repo here https://github.com/prism/PrismRefracted