How is this database structure designed?

language:+----------+------------------+| Field    | Type             |+----------+------------------+| id       | int(10) unsigned || language | varchar(45)      |+----------+------------------+country:+-------+------------------+| Field | Type             |+-------+------------------+| id    | int(10) unsigned || name  | varchar(45)      |+-------+------------------+goods:+--------------+------------------------+| Field        | Type                   |+--------------+------------------------+| id           | int(10) unsigned       || name         | varchar(200)           || model        | varchar(45)            || description  | varchar(200)           || price        | decimal(10,2) unsigned |+--------------+------------------------+

Demand:
1, 1 People do Commodity Information entry [basic information]
2, A, B, C countries for information localization, including Name,description,price and so on. The model is unique and does not need to be localized.
3, D countries found the language and basic information consistent, without localization, at this time read [basic information].
4, E countries can only localize prices, other information according to [basic information] to display.

Reply content:

language:+----------+------------------+| Field    | Type             |+----------+------------------+| id       | int(10) unsigned || language | varchar(45)      |+----------+------------------+country:+-------+------------------+| Field | Type             |+-------+------------------+| id    | int(10) unsigned || name  | varchar(45)      |+-------+------------------+goods:+--------------+------------------------+| Field        | Type                   |+--------------+------------------------+| id           | int(10) unsigned       || name         | varchar(200)           || model        | varchar(45)            || description  | varchar(200)           || price        | decimal(10,2) unsigned |+--------------+------------------------+

Demand:
1, 1 People do Commodity Information entry [basic information]
2, A, B, C countries for information localization, including Name,description,price and so on. The model is unique and does not need to be localized.
3, D countries found the language and basic information consistent, without localization, at this time read [basic information].
4, E countries can only localize prices, other information according to [basic information] to display.

Add Good_fields table (country_id,good_fields) to determine localized fields
Add a country_goods table (Country_id,goods) to store localized product information

Getting good information requires good_id and country_id
If you feel redundant too much you can consider serializing the Country_goods table to the JSON store

