Skip to content

Feature Comparison

Romans Malinovskis edited this page Aug 17, 2016 · 1 revision
Feature Use Case Eloquent Doctrine Cake3 ORM Agile Data
Entity to Query Builder Based on your entity, produce a query then tweak it, such as adding Grouping $m->action('select');
Field into Expression Can a specific field or expression be converted into part of the query (expression), such as inside sub-query. yes
Expressive conditions Can a complex and unsupported code be used inside load conditions? yes
Entity to Join multiple tables Entity information is located in multiple tables that must be loaded or updated simultaniously yes
Single table inheritance Record contains some indication as to which class should be used http://docs.doctrine-project.org/projects/doctrine-orm/en/latest/reference/inheritance-mapping.html#design-time-considerations yes
Class table inheritance Depending on class, main table may join more tables http://docs.doctrine-project.org/projects/doctrine-orm/en/latest/reference/inheritance-mapping.html#design-time-considerations yes
Inheritance Mapping Override Change table / join logic in derrived class. http://docs.doctrine-project.org/projects/doctrine-orm/en/latest/reference/inheritance-mapping.html#design-time-considerations yes
Calculated Aggregate Fields Field value is calculated using sub-select yes
Relation-based expression Relation is used to express sub-query for expression yes
Field re-naming When entity is stored in multiple tables, some fields names may clash. Will framework resolve this? yes
Aliasing When joining tables or using sub-selects, sometimes same table name can be used. Will framework come up with unique alias? yes