Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in
haskell-gargantext
haskell-gargantext
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 175
    • Issues 175
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 9
    • Merge Requests 9
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • gargantext
  • haskell-gargantexthaskell-gargantext
  • Issues
  • #404

Closed
Open
Opened Sep 26, 2024 by Yoelis Acourt@yacourt
  • Report abuse
  • New issue
Report abuse New issue

Database grooming

There is several actions that we can take to simplify the db usage and maintenance. The first low hanging fruit is the removal of empty tables.

node_node_ngrams2
nodes_nodes
nodescontexts_nodescontexts
rights

The second one is to improve the naming of the migration files (<incremental_id>_what_it_does.sql) and apply the patches on top of <0>_schema.sql stripped from the instructions which are already in the migration files. We would apply those in order to inialize a new db.

Edited Sep 26, 2024 by Yoelis Acourt
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
0
Labels
None
Assign labels
  • View project labels
Reference: gargantext/haskell-gargantext#404