I am attaching a zip file containing two sql files. Both contain very similarly sized and similarly structured databases of sports results. I need to move all of the results from "[url removed, login to view]" into "[url removed, login to view]". There are several important things to note so I will list them one-by-one:
1. The lookup table "lifts" does not need to be migrated, it is basically the same in each db
2. The lookup table "weightclass" is very similar but there are slight differences. Three tables in "[url removed, login to view]" do not exist in the other db. You can create new rows/ids for them. I've attached a document to explain which weight class ids go with which and also which three need to be created in "[url removed, login to view]".
3. While the database structures are very similar, you will find some differences in the "lifters" table. When creating new lifters in the "[url removed, login to view]" database, please transfer "full_name" to "iwfname".
4. Most of the tables in the database to be migrated can simply be moved as in without any sort of merge or anything beyond creation of new ids and managing the changes of those ids in the tables (ie, if meets get a new id, that will need to be adjusted without disturbing the other meet with that id, etc). There are no overlaps in the meets, attempts or weights tables so there is no merging that needs to be done there.
5. The "lifters" table will require the most work on your end. The reason is that there is significant overlap between lifters in both dbs. I would like for you to apply the following rules. If a lifter has the same birthday (ignore January 1st birthdates), country and gender as a lifter in the other database, please present all of those to me on a screen in the migration script. I should then have the option to merge the results or to create a new id. Some helpful information should be shown to me by each name (ie, name, country, how much they've weighed, how much they've lifted) to help me decide if they are the same person or not. If a lifter does not meet the above conditions (birthdate, country & gender), simply create a new id for them and I will find other ways later on to try to find any duplicates that may have slipped through. Do not pay attention to name in the "matching" process as names are often presented differently -- birthdate, country and gender are much more reliable data points.
6. These two databases are just 2009 and 2010. My actual databases are much bigger. I'm just giving you 2009 and 2010 to make this more manageable. But, as I need to merge my bigger databases, the deliverables for this project are a script that works to merge my databases.
Please let me know if you have any additional questions. This is a relatively simple project as there is not any tricky logic. It will take a few minutes to code but I think it's straightforward.
"slight differences. Three tables in "wl-small"
"slight differences. Three rows in "wl-small"