I don’t think of it as a database. It should say I have a good understanding of relations. Reasonable relations should exist in any application, not only in a database. But I understand that Blender has grown and not everything is as expected as if designed from the start.
Imagine there is a family consisting of whatever number of members. They can have 0 or many photo albums. There can pictures of any member in any photo album, and a photo album can contain pictures of different members. Nobody has to hold the albums. They are just lying there in the family’s house. The number of photo albums has no relation to the number of family members.
What Blender enforces is that every album must be held by a family member, and every member can hold only one album. Consequently, if you want more foto albums than family members, you have a problem. You would have to “produce” a new family member that can hold an album. That additional member is not really wanted because it is just there to hold an album. And there’s the not-answerable question which member should hold which album. That’s why this enforcement does not make sense.
(oh, just in case: this is only an analogy!)