I want to improve a database for product registration system. The goal of the system is to register products with characteristics. (length, height, color, max speed, weight, power etc. ) Each product has different characteristics. For instance, a car is registered with 30 number of characteristics length, height, max speed, etc. But a motor is registered with 6 number of characteristics such as power, weight etc.
The current architecture of database is so:
The main table is "registration". (the core of DB) Each product is described by a table. (because of different number of characteristics) For instance: Auto, Motor, etc.
Each charachteristecs are listed as attributes of this product table. For Auto: length, height, max speed, car year, car model ...
Now the problem is: The tables (products) are increased enormously, ie. too many tables.....
How can be solved this problem?

Thanks in advance!

What's wrong with lots of tables?

The tables (products) are increased enormously... At least invisible. Is the logic of the architecture right at all?

yes, it is right

do a search for subtype/supertype