Data modeling. How to simulate hundreds of dependent fields, 1: n or as a single table?

Question

I have to store leasing cars that come with progressive progressive maintenance costs, for example:

Basic data:

Id:    123  
Model: Ford Transit
yom:   2013

finished spending on a variable:

kilometers/year utilities  tires service misc
        10,000        80     400      50   30
        12,000       100     400      55   35
        14,000       120     400      60   40
          ...
       100,000       500   1,500     150  100

Thus, at a scale of 10,000 to 100,000 in increments of 2000 and 4 different types of costs, this leads to data fields of size 50 x 4 = 200.

Is it better to simulate this as a 1: n ratio, or is it normal to have more than 200 columns on my car table (MySql)? What are the pros and cons?

In case 1: n, will the trigger make sense to create 200 fields in the variable cost table when entering a new car record?

in advance for any hint

Answer 1

, 10 000 100 000 2000 4 50 x 4 = 200.

. , 200 4 .

1: n, 200 (MySql)?

, , 1:: n.

(, , 200 ).

?

, () , () [ , ], (c) (d ) [/ ] (e) . , .

1: n, 200 ?

. , , - . .

200 , .

, , ACID, . , 4 , , , "".

, .

• , .

  • Eg. Ford Transit Atomic, Atomic, Manufacturer Model.

• / :

  • Maintenance (Kilometre),

  • - , . , , .. .

• Relational Keys , , . , . :

  • A Model (, Transit) , a Manufacturer (, Ford).

  • A ModelYear (, 2013) , a Model (, Ford Transit).

  • , , .

• The Maintenance CHECK, , Kilometre 2000.

IDEF1X. IDEF1X . , , ; ; ; ; ; ; - . . IDEF1X. , .

, , , . , , , . , , False Teachers. , .

:
, .

, , , , - . ISAM 1970 2, , " ".

Relational Integrity, Power Speed, . - , . , .

Answer 2

, ( ). ()