Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
skeema pull deletes dir for ignored schema #55
I have a
But every time I run
Is this the intended behaviour? How can I prevent skeema from deleting it?
Also I haven't found a recommended workflow for test environments: https://github.com/skeema/skeema/blob/master/doc/examples.md#advanced-configuration
In traditional db-migration tools with up-down migrations, we'd use a different schema name (like
What's the skeema way of doing so? How do I keep
Thank you for the report! I can confirm the first part is a bug in
(I'm also tweaking the issue subject here just to clarify the directory is being deleted, not your actual database
Regarding your second question, the way to handle this in Skeema is to have a single directory, no need for symlinks. You just need to manually edit the .skeema file there to map the schema names correctly:
One question though -- do you just have one production schema, or several? If you only have one, I would recommend "flattening" the dir structure, so that there's no host-level parent dir, and the host/port/socket is defined in the same .skeema file as the schema name. Skeema will default to this automatically if you start with
If you have multiple production schemas, the correct layout is a bit harder to achieve, but still doable. If so, let me know more about your db layout, and I'm happy to help figure out the right config to match.
There are multiple production schemas.
Different people in the team have other temporary schemas in their local db. The production has some of them too that are not being used anymore. Those all are declared in
This is my current layout:
So , if I understand it correctly now, I actually don't need a separate
added a commit
Jan 9, 2019
Yes, that's correct. If
Separately, regarding the issue of