Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • dcdb dcdb
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 7
    • Issues 7
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • dcdb
  • dcdbdcdb
  • Issues
  • #20

Closed
Open
Created Aug 06, 2019 by Michael Ott@ottmiOwner

Introduce separate table for sensor meta data

Move all sensor meta data from the publishedsensors table to a separate table. The publishedsensors table would then only be used to really publish sensors (and hide others) and create aliases, whereas the new meta data table would hold information also about hidden sensors.

Fields in the meta data table:

  • SID
  • Unit
  • Factor

How should the virtual sensor be handled? In a separate table?

Assignee
Assign to
Time tracking