| Build Number | Database | OS |
|---|
| 3128 | MySQL | Windows Server 2019 |
The scenario looks like this:
We have this BSV called "AcmeA" that we built for Company A.
At one point in time when we were less experienced with AwareIM, another company wanted to use the same app but with their own data, so we created a new BSV called "AcmeB" for Company B.
In the beginning, when AcmeA received changes, we would also publish these for AcmeB.
However, at one point we decide to fork the applications because it was hard to develop things that would suit both companies as they were moving in different directions, and we had issues at the time to develop with modularity in mind.
So AcmeA would receive a ton of new updates, while AcmeB remained mostly static, or got some basic changes that AcmeA did not get.
Today we have built AcmeA in a more modular way to suit more companies, and we wish to push all these changes to AcmeB so they can reap the benefits of the new functions. I of course did expect to receive some interesting problems when I tried to push the AcmeA BSV as a new minor for AcmeB, but not like this.
So basically, when putting the BSV in testing mode, i got errors like this:
This did not really make any sense. So if I instead clicked "Publish", and then clicked "Review Database Changes...", I got really confused.
The changes AwareIM wanted to do:
Deleted objects: I can see a few database tables here that exist in both BSVs that share the same name, so it doesn't make any sense why they should get deleted.
Renamed objects: It says things like "Old name: Apples New name: "Oranges". This does not make sense either because these are completely different tables that have nothing to do with eachother.
New objects: I can see a few table names here that definitely exist in both versions, so it makes little sense why they would need to be created.
Change objects: Many objects are listed here, makes sense. Could be correct.
So why is there such a mismatch where AwareIM does not understand that a table named "Apples" in an older BSV is actually the same as "Apples" in a newer BSV and not "Oranges"? Is there some secret table somewhere that assigns IDs to the table names and interferes with the publishing?
EDIT: Found this thread to be useful where AwareIM support explains how BSV behaves when publishing: Data loss when publishing BSV
So yes, seems like there is a hidden ID that keeps track on the tables. Maybe I have this problem because I am doing the testing on a separate machine. Will retry the process on the same server which seems to be recommended.
EDIT2: I get the exact same problems even when doing it on the same server.
