Level 74
That sounds to me like a very bad database design. These kinds of values should have their own columns in a dedicated table.
- postcode
- number
- birthday
Sep 22, 2023
3
Level 1
Relationship: Using a database property table (Entity-Attribute-Value model)
I have a database structure such that a table account has properties in a table called accountPropertyValue. accountPropertyValue has an accountId column, a propertyId column (this relates to each property available, such as postcode, number, birthday etc.) and valueText, valueInteger and valueDate columns as well as a dataType column to know which valueX column to use.
Is there a nice way to build this relationship into Eloquent such that each property with propertyId x has it's own one-to-one relationship with account. Most is achievable by extending the hasOne class and creating a lot of custom rules but it would be nice to have this working more neatly. Thanks
Level 1
Hi @Tray2 There are over 100 very sparse 'columns' and it is a very old database so the EAV model made a lot of sense for us. We are looking at migrating to a fresh database in the coming years where we will look into removing any EAV structure's. Thanks
Level 3
It sounds like a polymorphic one-to-one.
https://laravel.com/docs/10.x/eloquent-relationships#one-to-one-polymorphic-relations
There is virtue to such a structure if your list of properties is going to grow over time, be user-defined, etc.
I've handled casting of value fields by using a single column of JSON type ... kind of a fun experiment and surprisingly powerful, but definitely requiring some extra care in querying, etc.
1 like
Please or to participate in this conversation.