Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Field Day Field Day
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 15
    • Issues 15
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Field Science
  • Field DayField Day
  • Issues
  • #12

Closed
Open
Created Jun 06, 2016 by Craig Earley@craigOwner

Separate uploading stream & sample data to server from deleting the local database

Make uploading the data a separate action from deleting the local database records. As it stands now if there is silent failure in the upload process then all the data is lost. Disk space on the device is cheap, human time to collect data is expensive. The database state indicator could play into this.

Assignee
Assign to
Time tracking