github-starred/vaultwarden
2
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-08-26 11:55:50 -05:00
Code Issues 534 Packages Projects Releases 86 Wiki Activity

about migration && schema.rs path #589

New Issue
Closed
opened 2025-11-07 06:42:07 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-07 06:42:07 -06:00
Owner
Copy Link
Copy Source

Originally created by @insub on GitHub (Jan 31, 2020).

Subject of the issue

I use sqlite db on development and mysql db on production.
If i run diesel migration generate <name> (like bitwarden_rs's wiki)
the migration file generate and put in "migrations/" , but not "migrations/sqlite",
so i have to run diesel migration generate <name> --migration-dir migrations/sqlite

The same happens when you execute build, the schema.rs generate and put in "src/db/", not "src/db/schemas/sqlite"

Your environment

MacOS 10.15.3

  • Bitwarden_rs version:
    v1.13.1

Steps to reproduce

diesel migration generate <name>
cargo run --features sqlite

Expected behaviour

schema.rs put in "src/db/schemas/sqlite"

Actual behaviour

schema.rs put in "src/db"

Originally created by @insub on GitHub (Jan 31, 2020). ### Subject of the issue I use sqlite db on development and mysql db on production. If i run `diesel migration generate <name>` (like bitwarden_rs's wiki) the migration file generate and put in "migrations/" , but not "migrations/sqlite", so i have to run `diesel migration generate <name> --migration-dir migrations/sqlite` The same happens when you execute build, the schema.rs generate and put in "src/db/", not "src/db/schemas/sqlite" ### Your environment MacOS 10.15.3 * Bitwarden_rs version: v1.13.1 ### Steps to reproduce `diesel migration generate <name>` `cargo run --features sqlite` ### Expected behaviour schema.rs put in "src/db/schemas/sqlite" ### Actual behaviour schema.rs put in "src/db"
GiteaMirror commented 2025-11-07 06:42:08 -06:00
Author
Owner
Copy Link
Copy Source

@dani-garcia commented on GitHub (Feb 4, 2020):

Yeah, it's one of the quirks of trying to work with a SQL library that isn't very focused in supporting multiple databases simultaneously, you'll have to handle the moving files to their respective folders and also generating those different schemas and migrations per database. I don't think there's much we can do about it

@dani-garcia commented on GitHub (Feb 4, 2020): Yeah, it's one of the quirks of trying to work with a SQL library that isn't very focused in supporting multiple databases simultaneously, you'll have to handle the moving files to their respective folders and also generating those different schemas and migrations per database. I don't think there's much we can do about it
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
better for forum
bug
documentation
duplicate
enhancement
future Vault
good first issue
help wanted
low priority
notes
pull-request
Mirrored from GitHub Pull Request
 question
SSO
Third party
troubleshooting
wontfix
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vaultwarden#589