Benefit

Hello, Drupal is excellent and has given us a variety of solutions. Programmers are required to design according to project requirements. The Easy entity base field module can work together with the Field module in the core without affecting each other. Programmers can choose which fields belong to The base table or use an independent field table. For projects with a small amount of data, the Easy entity base field may be a good solution.

The original intention of the design is that my project needs a lot of data types. ECK has not been updated for a long time, so I designed a module that can easily create entity types. After creation, use Easy entity base field to add base fields, which solves unnecessary repetitive work.

Hi,

You wrotte:
Programmers can choose which fields belong to The base table or use an independent field table.

But how?
TY

My understanding is that classification design can be done according to the data type, for example, user entities: name, gender, age can be placed in the base table.

For example, working experience: company name, business scope, entry time, position, departure time and many other fields, and there will definitely be multiple pieces of data, which requires the establishment of a new entity type, using entity references, Dynamic Entity Reference fields to achieve association, or It is a custom field to achieve.

For small and medium-sized projects, the impact on performance is actually not too great. For applications with millions or tens of millions of data, more advanced performance optimization solutions are needed.

Now popular micro-services can create multiple micro-application services based on application data types, and use APIs for data exchange, that the single-table approach is more clean and friendly.

I fully support the purpose of this module: when having a lot of fields, the core drupal approach without coding is to add one table per field and this has a significant impact on performances on large site (also making the DB not manageable with hundreds of tables), and using caching mechanisms is a workaround and need (a lot of) storage. To retrieve an entity, joining N tables is much slower than retrieving N columns from the same table in relational database, even if the N tables have indexes
So the possibiity to add common fields as properties to the base table is very useful.
Thanks to the maintainer :)