Skip to content

Possible issue when updating messages. #1

@aaron-iz

Description

@aaron-iz

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.
  1. Create an instance of the API.
  2. Create a table.
  3. Remove the table.
  4. 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

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions