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

Import v2 tables into v3 DB as-is to ensure no data is lost #3419

Open
rjmackay opened this Issue Dec 2, 2018 · 2 comments

Comments

Projects
None yet
1 participant
@rjmackay
Member

rjmackay commented Dec 2, 2018

  • As a deployer I need to know I will not lose any data when migrating to v3
  • As Ushahidi staff, I need to know I will have all v2 data available in future in case some data is lost

Approach:

  • Grab a list of tables from the DB
  • Grab the schema for each one and create a new table in our v3 DB names v2_TABLENAME
  • Copy all the data, maybe through INSERT INTO ... SELECT
@rjmackay

This comment has been minimized.

Member

rjmackay commented Dec 2, 2018

  • As a deployer I need to know I will not lose any data when migrating to v3
  • As Ushahidi staff, I need to know I will have all v2 data available in future in case some data is lost
@rjmackay

This comment has been minimized.

Member

rjmackay commented Dec 11, 2018

@willdoran does this seem like a reasonable way to preserve the original data? Basically I want to copy everything blindly, rather than a known set of tables, in case there are extras for plugins etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment