Components - HomeroThompson/firehawk GitHub Wiki

Components

In terms of OOP value objects are mapped as components. These components can be mapped to the same table as the parent entity (for one-to-one relationships) or can be mapped to a separate table for (one-to-many relationships).

When the components are mapped to a separate table Firehawk lets you choose the convention that will generate the names for these tables. It is recommended to customize component table names since many entities can use the same value object class and it could lead to name collisions if we left the table name be the same as the component name.

As stated previously, for one-to-one relationships NH will map the component into the same table as the parent entity. In this case Firehawk lets you choose the convention used when the component column names are generated.

[Tables] [Columns]