Compare Sizes
Français Español


Simple: no magic inside : it’s basically SQL queries
PHP Data Access Libraries (ORM, ActiveRecord, Persistence)
Github / Bitbucket /
LicenseApache 2
Latest version3.4.2
How schema is defined?PHP
Code generation
Can be used in Any FrameworkYes composer / packagist
Automated Cache
Anti-patterns (purposely included)
DependenciesMinimal: 3, pimple, doctrine/cache, aura/sqlquery
5.0/5 1 rating
Enterprise Compliance
5.0/5 1 rating
Minimum PHP Version5.5
Basic Features
PDO Support- But made a custom driver to support it is easy
Transparent support for NoSQLNo
How to invoke db-vendor-specific extensions?Yes Ting use native query, you can use everyting of your SGBD
Array as a persistence
RestAPI as a persistence
JSON string as a persistence
Same model, multiple persistences
Basic Single-record operations (C,R,U,D)
Table Name MappingYes Yes
Field Name MappingYes Yes
Map Entity to SubQueryNo This concept is no-sense for Ting
Map property to expressionNo This concept is no-sense for Ting
Map native types (DateTime)Yes Yes
User-defined types (e.g. "23 USD")Yes Yes, with custom serializer
Map field of related Entity ('currency' = currency_id->Model Yes
Map field to sub-query on related entity (Client.balance = Client->orders->sum(total))- This concept is no-sense for Ting
Entity to join multiple tables (adding new record populates both tables)Yes Yes
Criteria, Scope, Conditions (Model will refuse to work with records that does not match criteria)
Support model-level criteria
Domain Model Criteria
Expression-based condition
Criteria Compliance (new record must match condition)
Dynamic criteria
Query Building (Convert Model into Query object for further SQL tweaking)
Convert Model into Query Object
Raw expressionYes
Nested/Composite Queries/Expressions
Reference domain-model field in queryNo
field, where, order, limitYes
options, rollup, partition
UPDATE, DELETE, INSERT query buildingYes
ALTER, CREATE query building
User-defined query template
full support for OR conditions
Use Domain logic in multi-record update
Data Fetching (different ways to retrieve data from database)
Get All Data (2x array)Yes
Associative Array (id=>value)
Select only required fields
Typecasting (e.g. DateTime)Yes
Import (multiple records)Yes
Respect domain model mapping (and criteria)
Single rowYes
Single ValueYes
Single ColumnYes
Bypass persistence mapping
Loading and Saving individual records
Load by IDYes get(id)
Load by other fieldYes getBy(['propertyName' => 'value']);
Read-only Models
Model without primary keyYes
Specify fields to loadYes
Save only sends dirty fieldsYes
Guarded / Fillable properties
Object Hierarchy Model
Admin extends User, adds criteria (is_admin=1)
Admin extends User, adds accessible fields
Extend model, add Join (Disjoined SubTypes)
Extend model change table
Relations/References (One model can relate to another model. NOT A TABLE JOIN)
Model can define relation to other Model
One-to-many traversal strategy
Deep Many-to-Many traversal.
Cross-Persistence traversal
Cross-persistence joins, aggregation, reporting
Multi-persistence join
UNION existing models
Domain-model Aggregation
Model to Model join
Multi-persistence UNION
Behaviours / Hooks
Before/After operation
Override standard C,R,U,D operations
Persistence-specific hooks (to modify Query)
User-defined hooks
Global Auditing
Store old/new field values
Revert action (undo) and replay (redo)
Reactive actions
Store log in any persistence
Override, Add fields to audit log
Custom events
Access to record-specific history
Date of creation, modification
User/IP creation, modification
Store incremental revisions
Field meta-information provided
UI extensions
API extensions
Dec. 21st 2017 11:31:25 AM
View changes

User reviews and comments

No comments yet. Be the first to leave your review.