Now I ran into another release with multiple albumartists - it's really time to get this implemented... ;-)
I'm pretty sure I have some more...
This is indeed a very interesting feature which has been discussed previously.
The biggest challanges with implementing this feature is:
1) Create smart loging during adding and updating of albums so that they map to the exact artists
2) Being able to visualize an album for more than one artist (applies to views, searches etc)
3) Performance. Introducing a new mapping between an album and the artist table will slow things down. This is the most important point, to analyse exactly how much the performance will be affected.
As you can see from above, it is not a small fix, it will have impact on the most of Heliums functions, still worth to analyse though.
Performance will be affected since at least two additional joins will be needed, but as mentioned before, it will need to be benchmarked more in detail to see the actula impact.
I agree this request.
Hitting yet again on such a release and still hoping to see this feature any time soon(er or later)...
This will be re-reviewed when SQL Server Compact is fully removed and compared to other waiting things in our backlog (usability/request rate vs time to market).
But indeed it would be a nice thing to have, but it will break things a lot, thus it is a bit expensive to implement.
Yes, I know it's a big change - but I think it's a must-have... ;-)