Issue Title: Possible issue when updating messages.
Description
- A day after creating two example tables (channels), I used the bundled CLI client to drop them. The tables were successfully dropped (channels were removed). However, %meta_quildedsql% was not updated accordingly, and the corresponding channel ids persisted regardless being deleted. Upon restarting the client, it failed to load the tables/channels since they were deleted, resulting in a 404 error and a crash.
- After trying to reproduce immediately, it worked OK, and meta was updated properly. I had a suspicion that there is a time period after creating a message, during which you can update the message. Once this period has passed, updates are no longer allowed, but it seems unlikely to be the case.
Steps to Reproduce
- Note: could not reproduce immediately.
- Create an instance of the API.
- Create a table.
- Remove the table.
- Restart the API.
Expected Behavior
The tables should not be loaded if deleted previously.
When client drops a table, the abstracted channel must be deleted, and the channel's guilded identifier should be removed from any message they appear on %meta_quildedsql%
Actual Behavior
Inconsistent.
Additional Information
Looking at the API could not find anything about it
Issue Title: Possible issue when updating messages.
Description
Steps to Reproduce
Expected Behavior
The tables should not be loaded if deleted previously.
When client drops a table, the abstracted channel must be deleted, and the channel's guilded identifier should be removed from any message they appear on
%meta_quildedsql%Actual Behavior
Inconsistent.
Additional Information
Looking at the API could not find anything about it