Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • pleroma pleroma
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 653
    • Issues 653
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 98
    • Merge requests 98
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PleromaPleroma
  • pleromapleroma
  • Issues
  • #1304
Closed
Open
Issue created Oct 07, 2019 by rinpatch@rinpatchContributor

Stop using `user.info`

  1. It's not much more convenient than just having separate fields
  2. Fields in it are harder to index due to them being jsonb, so even using an indexed boolean from there screws with the query plans. Also things like mutes and blocks not being proper relations slows things down.
  3. Migrations are easier and faster to perform when they are not inside of jsonb
  4. You can't wipe everything with unsafe use of jsonb_set

Thus, I think we should stop using user.info for new fields, and migrate old fields out of it over time.

cc: @kaniini @lambadalambda

Edited Oct 07, 2019 by rinpatch
Assignee
Assign to
Time tracking