how does RAM store artifact versions across different asset versions?
Lets say I have an asset called asset1, and it has 3 artifacts within it:
1. a.zip -> binary zip file
2. b.txt -> simply text file
3. c.exe -> binary executable
Then I create a new version, and I make the following changes to the artifacts list:
1. Add a new version of a.zip .
2. Add a new version of b.txt.
3. Add a new file called d.txt.
In the repository, how would this change look? I assume the following:
1. There would be two full versions of a.zip, one each associated with the two versions of the asset1 asset.
2. There would be a full version of b.txt associated with the first version of asset1, and then some sort of delta identifier for it that would be stored with the second version of the asset.
3. There would be one version of c.exe associated with both versions of the asset.
4. There would be one version of d.txt associated with the second version of the asset.
Can someone confirm that this is how RAM does its backend storage.
Thanks.
1. a.zip -> binary zip file
2. b.txt -> simply text file
3. c.exe -> binary executable
Then I create a new version, and I make the following changes to the artifacts list:
1. Add a new version of a.zip .
2. Add a new version of b.txt.
3. Add a new file called d.txt.
In the repository, how would this change look? I assume the following:
1. There would be two full versions of a.zip, one each associated with the two versions of the asset1 asset.
2. There would be a full version of b.txt associated with the first version of asset1, and then some sort of delta identifier for it that would be stored with the second version of the asset.
3. There would be one version of c.exe associated with both versions of the asset.
4. There would be one version of d.txt associated with the second version of the asset.
Can someone confirm that this is how RAM does its backend storage.
Thanks.