Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • W waLBerla
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 52
    • Issues 52
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 14
    • Merge requests 14
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • waLBerla
  • waLBerla
  • Issues
  • #97
Closed
Open
Issue created Aug 16, 2019 by Dominik Thoennes@thoennesOwner

move sqlite from postprocessing

sqlite is currently located in module postprocessing. However, it only depends on core. Since postprocessing depends on domain_decomposition, field, python_coupling, stencil and geometry one hast to build all these modules even if only using sqlite (as we are doing in HyTeG). Therefore I would like to move sqlite into its own module. Any thoughts against this?

Assignee
Assign to
Time tracking