My table
book
Where pfk - Primary-Foreign Key;
{ID, langID} - PK;
chaptersPrice - price of each chapter of book. Example:
BookName1:
BookName2:
I think in this table some attributes are functionally dependent on the part of primary key (ID):
{ID} -> {releaseYear}
{ID} -> {chaptersPrice}
{ID} -> {thumbnail}
Should I implement it like this
book
book_attrs
Then book and book_attrs have "one-to-many" relationship
Some considerations may depend on your use-case / domain model.
releaseYear of a book typically does not change (in simple cases), so it could be in BOOK table.
From a 'book store' perspective, 'price' could be in a different table, as that would be updated based on market conditions.