Skip to content

Split Textpacks into 3 (admin, common, public)? #1576

Description

@philwareham

Would there be any performance benefit (public side) from splitting Textpacks into three tables (admin, common, public) in future? As far as I can ascertain the whole Textpack table is read on the public side when only the public and common sections are needed.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions