php - Symfony form large data set

Question

For a Symfony 4 project we need to make a large inpection form about surfaces with many fields. We're looking for the approach how to organize the structure and relationships and keep load speed in mind.

I've created the basic entity example below, which is still simple to be stored in one database table. The fields below are simple relations or string fields so a InspectionType would be easy.

class Inspection
{
    /** @var string */
    protected $projectName;

    /** @var string */
    protected $projectPlace;

    /** @var User */
    protected $inpector;

    /** @var Customer */
    protected $customer;

    /** @var string */
    protected $conclusion;

    /** @var string */
    protected $advice;

    // Complex part
    
    /** @var Collection */
    protected $surfaces;
}

Now for the complex part. Each inspection could contain one or more surfaces (ArrayCollection). Each surface consists of different fields, see below:

• Roof surface (4 fields);

1. text type
2. choice type (single)
3. choice type (multiple)
4. date type

• Leakage (3 fields);

1. text type
2. images (relation, OneToMany)
3. choice type (single)

• Tension (3 fields);
• Slope (3 fields);
• Roof Pollution (3 fields);
• Damage (5 fields);
• Ballast (3 fields);
• Eaves (3 fields);
• UprightWork (4 fields);
• Dilation Rebellion (5 fields);
• Chimney (3 fields);
• Shunt Box (3 fields);
• ... 9 more+;

My question how to setup surfaces and database structure, should each part in a surface have its on table like below with a relation back to inspection (this would create many tables, is this bad?):

• table inpection
• table inpection_leakage
• table inpection_tension
• ...

I was thinking to create an Embed Collection Form like below

class InspectionType extends AbstractType
{
    public function buildForm(FormBuilderInterface $builder, array $options)
    {
        // ...

        $builder->add('surfaces', CollectionType::class, [
            'entry_type' => SurfaceType::class,
            'entry_options' => ['label' => false],
        ]);
    }
}

class SurfaceType extends AbstractType
{
    public function buildForm(FormBuilderInterface $builder, array $options)
    {
        $builder->add('leakage', LeakageTyoe::class);
        $builder->add('tension', Tension::class);
        $builder->add('slope', Slope::class);
        ...
    }
}

Is this the way :) to go

Answer 1

I would suggest to use a discriminator/inheritance map for your surfaces entity, with a single_table strategy. This gives you the speed and flexibility you need.