Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • Tryton Tryton
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 808
    • Issues 808
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 107
    • Merge requests 107
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • External wiki
    • External wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • TrytonTryton
  • TrytonTryton
  • Issues
  • #5563
Closed
Open
Issue created May 20, 2016 by Luis Falcon@meanmicio

Scalability issues in party address subdivision

The current design on party address does not scale, since anytime the party model is accessed, it selects all the subdivisions for that country[1]. The performance degradation is such that it makes the system unusable even with reasonably small number of subdivisions.


1.- SELECT "a"."id" AS "id" FROM "country_subdivision" AS "a" WHERE (("a"."country" = 22)) ORDER BY "a"."code" ASC, "a"."id" ASC

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking