![Wink ;-)](https://dt9qzg9h465rt.cloudfront.net/phpBB3/images/smilies/icon_e_wink.gif)
I'm building an app to manage musical events, strictly inhouse use and for our times, "miniature" table sizes and almost no need for super performance . The idea is primarily to hold almost any information in the db, later on to generate all sorts of files which are needed...
A certain part is clear enough, you have seasons, concerts, locations, ensembles, artists, instruments, composers, opera...
The relation between concert, ensembles and artists is by nature N:M, so i'll need intermediate tables.
Now, there are e.g. concerts with
* one artist,
* with N artists, which form an ensemble,
* with N artists which don't do this,
* with N ensembles and
* with N ensembles plus M artists, which don't belong to any of them.
Somehow i'm stuck how to model this, and especially, how to build a gui for maintainance.
Helpful thoughts anyone?