Skip to content

Potentially restructure the factoids database #399

@ajax146

Description

@ajax146

The current factoids database is being stretched to it's limits, especially with aliases

Rewriting the database structure to be something like the following 3 tables:

Table: factoids
UUID    guild_id    plaintext_message    json    creation_time     hidden

Table: calls
UUID    guild_id     call_text     factoids_UUID

Table: jobs
UUID    factoids_UUID    channel    cron_config

This would allow a much more robust and easier-to-use database structure. It would be easier to modify and expand the factoids extension further if we choose to.

This is not a high priority, but something to think about
This would require a pretty much fundamental rewrite of the factoids system

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions