Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • cubicweb cubicweb
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 232
    • Issues 232
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 16
    • Merge requests 16
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • 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
  • cubicweb
  • cubicwebcubicweb
  • Issues
  • #202
Closed
Open
Created Jan 15, 2021 by Arthur Lutz@arthurOwner

db-create without --drop runs DROP if in --automatic

Reading the --help of db-create, I am lead to believe that if I want to drop an existing database, I have to use --drop. It seems that using --automatic also runs the DROP https://forge.extranet.logilab.fr/cubicweb/cubicweb/-/blob/branch/default/cubicweb/server/serverctl.py#L374

I think I got bitten by that bug since we're trying to create databases on the fly on review apps deployments of cubicweb on a kubernetes cluster. I would like for db-create to fail when the database already exists. Or am I using the wrong command ?

Edited Jan 15, 2021 by Arthur Lutz
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking