You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 18, 2019. It is now read-only.
So I was just wanted to point out that currently, the importing of schemas into the mysql database backend destroys the tables, if they exist, before creating them, as it is meant to.
My issue is that this implementation makes it difficult to create the Morgue backend when having to provision a new Morgue server while keeping the data from the old Morgue server.
So what I am wondering is, why go with this approach? Why not check if the tables to be created exist before creating them, and then skip creating them if they already exist and not destroying old data.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
So I was just wanted to point out that currently, the importing of schemas into the mysql database backend destroys the tables, if they exist, before creating them, as it is meant to.
My issue is that this implementation makes it difficult to create the Morgue backend when having to provision a new Morgue server while keeping the data from the old Morgue server.
So what I am wondering is, why go with this approach? Why not check if the tables to be created exist before creating them, and then skip creating them if they already exist and not destroying old data.
The text was updated successfully, but these errors were encountered: