Skip to content
GitLab
  • Menu
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 31
    • Issues 31
    • 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
  • LBMC
  • yvertlab
  • mylabstocksmylabstocks
  • Issues
  • #128
Closed
Open
Created Jun 23, 2021 by Gael Yvert@gyvertOwner

Make relationships compatible with Laravel convention

Currently, some dropdown menus use relationships to tables that are defined in the model, and passed to the BREAD via Voyager. or example, the supplier field of table antibodies provide a dropdown of names entered in the suppliers table.

The issue is that the antibodies table stores the name of the supplier and not the supplier_id. This results from the fact that in v1.0.0 we used to store names and we had to be compatible for migrating to v2.0.0.

We should now fix this to have clean and safe database structure and models.

Assignee
Assign to
Time tracking