Concerning normalization of a one to many relationship, I am not sure how to represent a collection with a specified capacity in a database. I can think of two ways to represent an entity A with a one-to-many relationship with B:
When Table A is created with n capacity, insert n rows into Table B. The amount of rows in Table B represents the capacity for that collection (Like allocating memory). These rows must be updated as elements are placed and removed from the collection.
When Table A is created with n capacity, represent the capacity as a column in A. Rows must be inserted and deleted from Table B as elements are placed and removed from the collection. The application ensures that table B has no more than n rows.
What are the benefits or detriments of each of these ways? Is there a standard method for doing this? Are there performance or maintenance concerns?