Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • mylabstocks mylabstocks
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 30
    • Issues 30
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • LBMCLBMC
  • yvertlabyvertlab
  • mylabstocksmylabstocks
  • Milestones
  • Make database modular
Open
Milestone

Make database modular

For the app to be safely customizable, it would be nice to distinguish different types of tables in the database:

  • "core tables": are common to all configurations, and remain always compatible with previous versions (eg, we never drop a column...)
  • "modules tables": are instance-specific. For example, tables of nematodes, used only in nematode labs.
  • ...

Even better if we later have the possibility to move a "module table" to the set of "core tables".

Assign some issues to this milestone.
  • Issues 0
  • Merge requests 0
  • Participants 0
  • Labels 0
0% complete
0%
Start date
No start date
None
Due date
No due date
0
Issues 0 New issue
Open: 0 Closed: 0
0
Merge requests 0
Open: 0 Closed: 0 Merged: 0
0
Releases
None
Reference: LBMC/yvertlab/mylabstocks%"Make database modular"