As opposed to track databases, album databases do not have a guaranteed one row to one item relationship. This may typically be the case but a row can also be a single disc if you are maintaining separate disc subfolders. If you have folders containing multiple albums or a single album is split into multiple folders (disc for example), issues can arise when updating the database. Issues can also arise if not all of an album is loaded when an update occurs.
The best way to get around these potential issues is to ensure that the Album field metadata is consistent for all tracks in a folder and that an album's folder contains all tracks in the album. Use the Disc field to differentiate discs. Additionally, ensure that an entire album is loaded when it is to be updated.
Some users like having separate Disc folders. If this is the case everything will work fine when updating the database as long as the containing folders do not change. If you're going to change the location, the best solution is to ensure that that tracks contain a Yate Album ID. When an album's location changes and a Yate Album ID is present it will be used to locate the database entry and allow the folder location in the database to be updated.
Note that Yate v8.1.1 changed the grouping of a Yate Album ID from the Album field to the containing folder. This fixes a number of issues where users maintained separate disc subfolders.