-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Find a way to provide and update migrations #19
Comments
what are the requirements for this? is this just a generator for https://github.com/samvera-labs/valkyrie-sequel/blob/26fddaf50045cb6c83d43c8699b1f56f7aa72895/db/migrations/001_create_orm_resources.rb, or is something more needed? |
The real issue is how to run those migrations against a given database configuration, I think. For instance - right now our test setup does
which then does valkyrie-sequel/lib/valkyrie/sequel/metadata_adapter.rb Lines 34 to 43 in a7c9411
but I sort of doubt that's actually the process we want? Like what if folks want to run their own migrations? Is it sufficient to add to the readme somewhere, "as part of deployment call Normally I'd test this in Figgy, but we actually have quite a few custom indexes and such and we migrated from the AR adapter to Sequel, so it's just running off all the old AR migrations. |
isn't it sufficient to point to EDIT: comet does https://gitlab.com/surfliner/surfliner/-/blob/trunk/comet/scripts/db-migrate-seed.sh#L7 |
I didn't know sequel -m existed! So maybe we just need a way to copy migrations locally? |
No description provided.
The text was updated successfully, but these errors were encountered: