2016-10-26 15:42:23
PHP Data Access Libraries (ORM, ActiveRecord, Persistence)
Github / Bitbucket / Sourceforge
Latest version
How schema is defined?Model class properties
Code generation
Can be used in Any FrameworkYes Through Capsule
Automated CacheYes
Anti-patterns (purposely included)Eloquent is a God Class; Global functions; DB Conection is global;
Simplicity0 no rating
Enterprise Compliance3.0 1 rating
Minimum PHP Version
Basic Features
PDO SupportYes
NoSQL Integrate TransparentlyNo Eloquent is built on Query Builder.
How to invoke db-vendor-specific extensions?Yes Through Query Builder / RAW queries.
Array as a persistence
RestAPI as a persistence
JSON string as a persistence
Same model, multiple persistences
Persistence Mapping (must support C,R,U,D)
Table Name MappingYes Same as model class name by default
Field Name Mapping- Through accessors/3rd party extension
Map Entity to SubQueryNo Must be physical table.
Map property to expressionNo Must be physical table
Map native types (DateTime)Yes Accessors and Mutators
User-defined types (e.g. "23 USD")Yes Accessors and Mutators
Map field of related Entity ('currency' = currency_id->Model Currency.name)- Relationship, but only single record.
Map field to sub-query on related entity (Client.balance = Client->orders->sum(total))No
Entity to join multiple tables (adding new record populates both tables)No
NoSQL (must be transparent to domain logic)
MongoDB supportNo
MemCache- Through Caching backend, but not as ORM native persistence.
Criteria, Scope, Conditions (Model will refuse to work with records that does not match criteria)
Support model-level criteria- Global Scope (querying only)
Soft-deleteYes Trait and Scope
Domain Model Criteria- Scopes, but not in domain model.
Expression-based conditionYes through Query Builder
Criteria Compliance (new record must match condition)
Dynamic criteria
Query Building (Convert Model into Query object for further SQL tweaking)
Convert Model into Query ObjectYes Model is a Query object. See: Model::where()
Raw expressionYes DB::raw()
Nested/Composite Queries/ExpressionsNo
Reference domain-model field in queryNo No fields. Only properties.
field, where, order, limitYes
options, rollup, partition
UPDATE, DELETE, INSERT query building
ALTER, CREATE query building
User-defined query template
OR deep nested conditions
Use Domain logic in multi-record updateNo
Data Fetching (different ways to retrieve data from database)
Get All Data (2x array)Yes
Associative Array (id=>value)Yes lists()
Single rowYes
Single ValueYes
Single ColumnYes
Bypass persistence mapping- ?? (e..g prevent date from being transformed into Carbon)
Loading and Saving individual records
Load by ID
Load by other field
Load if expression
Load respects Scope (model-level condition)
Specify fields to loadNo Fields load with SELECT *
Save only sends dirty fieldsYes
Guarded / Fillable propertiesYes Prevents "create($_GET)" from messing up important fields.
Object Hierarchy Model
Admin extends User (is_admin=1)No Both have to use "User" model.
Model that represent Orders of single User.No Both have to use "Order" model.
Extend model, add Join (Disjoined SubTypes)No
Extend model change table
Relations/References (One model can relate to another model. NOT A TABLE JOIN)
Model can define relation to other ModelYes Relations
One-to-many traversal strategyReturns array of objects that may either be pre-loaded with record data or only contain IDs (lazy-loaded).
Deep Many-to-Many traversal.
Cross-Persistence traversal
Multi-persistence Mapping (some data from SQL, others MongoDB)
Multi-persistence joinNo
UNION existing modelsNo
Multi-persistence UNIONNo
Multi-persistence value linking (current_sensor_value)
Behaviours / Hooks
Before/After operation
Hooks for C,R,U,D operations
Persistence-specific hooks (to modify Query)
User-defined hooks
Mapping strategy
How to set-up
Store old/new field values
Date of creation, modification
User/IP creation, modification
Store incremental revisionsYes
Revert action (undo)No
Custom events
Custom fields, table
Store in CSV
Access to record-specific history
Access Control
Implementation Strategy
Single-system global access scopeNo
Meta-information (allows exploration by UI widgets)
Implementation StrategyEloquent is designed to work with MVC engines, where view is mandatory and would be defining how model properties fit into your HTML.
UI Widget can fetch list of Model FieldsNo Would have to manually specify fields.
UI Widget can get Field type, default value, caption, hintNo
field storing reference to another Model can map into DropDownNo Must manually specify object with lists() method.
Like 0
  • 2016-10-18 22:11:55
    2016-10-26 15:42:23
  • Products
  • Public
  • Creative Commons License CC-BY-SA 3.0 / GNU FDL

Build comparison tables or lists about everything !

It's free and fast to publish data into original tables

Create a table