History of Agile Data

Last update Dec. 20^th 2017 1:05:19 AM

Creation date Oct. 18^th 2016 10:11:55 PM

Romans Malinovskis on Dec. 20^th 2017 1:05:19 AM
Field meta-information provided
Type, caption, possible values, mapped field, join table spec, encryption, serialization, UI-specific settings, validation rules.
UI extensions
yes CRUD, Form, Table, Grid, Entity-manager. (see https://github.com/atk4/ad)
API extensions
yes RestFULL API, automated CRUD operations + RPC https://github.com/atk4/api
UNION existing models
yes Yes, in add-on https://github.com/atk4/report/. Can join UNION result with more tables.
Romans Malinovskis on Dec. 19^th 2017 11:25:45 PM
Guarded / Fillable properties
yes Conditions and OnlyFields do same thing but more reliably.
UNION existing models
yes Yes, in add-on https://github.com/atk4/report/
Multi-persistence UNION
no
Domain-model Aggregation
yes Group by multiple fields. Apply aggregation functions. Preserve types.
Model to Model join
no Planned.
Multi-persistence join
no
Reactive actions
yes Each action will be automatically linked with sub-actions which may be invoked through Hooks.
Store log in any persistence
yes
Romans Malinovskis on Dec. 19^th 2017 9:41:37 PM
Typecasting (e.g. DateTime)
yes
Respect domain model mapping (and criteria)
yes
Select only required fields
yes
Import (multiple records)
yes
Single Value
yes Through action
Single Column
- may need to map resulting array
Read-only Models
yes Yes
Model without primary key
yes Yes, but only in Read-only Mode
Romans Malinovskis on Dec. 19^th 2017 9:22:55 PM
full support for OR conditions
yes Through Object Composition and Expressions
Romans Malinovskis on Dec. 19^th 2017 7:42:35 PM
Website
http://git.io/ad
Description
Data Access Framework for high-latency databases (Cloud SQL/NoSQL).
Latest version
1.2.x
How schema is defined?
in PHP. Method init() in Model class defines fields, relations, conditions, etc.
Code generation
yes https://github.com/atk4/schema
Automated Cache
yes Frameworks focuses on optimizing queries rather then caching. Still possible with cross-persistence saving.
Anti-patterns (purposely included)
Model close-coupled with Persistence and Field classes.
PDO Support
yes Yes
Transparent support for NoSQL
- Through 3rd party drivers.
How to invoke db-vendor-specific extensions?
yes For SQL - save/load/delete operations are expressed in DSQL Queries that can be manipulated: http://git.io/dsql
RestAPI as a persistence
- Through 3rd party extension.
JSON string as a persistence
yes Supported with few extra lines of code.
Table Name Mapping
yes Yes
Field Name Mapping
yes Yes (Field::actual property)
Map Entity to SubQuery
yes Yes. Extension exist for UNION-models. https://github.com/atk4/report
User-defined types (e.g. "23 USD")
yes Yes. Independent from Model. by extending Field class.
Map field of related Entity ('currency' = currency_id->Model Currency.name)
yes Transparently maps into sub-select.
Map field to sub-query on related entity (Client.balance = Client->orders->sum(total))
yes Yes. hasMany()->addField(..aggregate)
MongoDB support
- Extension.
Neo4j
- Extension.
MemCache
- Extenison.
Support model-level criteria
yes Yes. Applied on loading / saving / update.
Soft-delete
yes Through criteria. Example given in the docs.
Domain Model Criteria
yes $m->addCondition('gender','M'); where 'gender' can be arbitrary expression, sub-select, field from association(join) or mapped no another physical field.
Criteria Compliance (new record must match condition)
yes Transaction rollback and exception. Automated-rloading.
Romans Malinovskis on Oct. 24^th 2016 5:38:10 PM
Automated Cache
- Planned
Romans Malinovskis on Oct. 24^th 2016 5:09:26 PM
Support model-level criteria
yes
Romans Malinovskis on Oct. 24^th 2016 2:14:50 AM
Deep Many-to-Many traversal.
yes $user->ref('Orders')->ref('Payments')->action('count'); No intermediate queries.
Field meta-information provided
Define a special DB-hook. Every time new "Model" is initialized, extra "condition" will be added. This will make sure that you won't forget some important condition when traversing references. You can also restrict access to edit/delete through per-model hooks that can be globally set.
Romans Malinovskis on Oct. 24^th 2016 2:00:53 AM
How to invoke db-vendor-specific extensions?
yes Provides access to persistence-layer actions (Queries)
Romans Malinovskis on Oct. 21^st 2016 6:57:20 PM
Map Entity to SubQuery
yes "Table" can be "Expression" (or another Model)
options, rollup, partition
- Through custom templates, or expressions.
Romans Malinovskis on Oct. 19^th 2016 1:41:13 AM
Editor
public
Viewer
public
Romans Malinovskis on Oct. 19^th 2016 1:38:35 AM
Single Column
no Planned
Associative Array (id=>value)
no Planned
Romans Malinovskis on Oct. 19^th 2016 1:36:28 AM
Automated Cache
no Planned
Romans Malinovskis on Oct. 19^th 2016 1:33:39 AM
Implementation Strategy
Agile Data is designed to work with UI toolkits. Generic widgets can explore model fields and various meta-information about those fields. References are easy to identify and traverse allowing DropDown fields to populate values inside select.
UI Widget can fetch list of Model Fields
yes
UI Widget can get Field type, default value, caption, hint
yes
field storing reference to another Model can map into DropDown
yes Widget can discover references and traverse to fetch list of drop-down options. Model defines "title_field" which is used by default.
Field meta-information provided
Secure Enclave - extension to proxy "model" would allow un-safe 3rd party code to perform C.R.U.D operations as long as conditions are satisfied for a single model. This allows 3rd party code to discover part of your schema. Proxy can be configured with custom ACL rules on per-extension basis. Additional rules may be imposed based on user.
UI extensions
yes Define "system_id" for all models that have this field defined - this will create global condition for all models making sure that user can work with records of one system at a time.
Romans Malinovskis on Oct. 19^th 2016 1:06:17 AM
One-to-many traversal strategy
Returns destination model instance with dynamically applied criteria (parent_id=123). No queries are executed. Inserting record into this model will ensure association with parent model.
Automated Cache
no Anti-pattern
Anti-patterns (purposely included)
SRP in Model. Implements Scopes and Active Record.
User-defined types (e.g. "23 USD")
yes Through typecasting
Map field of related Entity ('currency' = currency_id->Model Currency.name)
yes Maps into sub-query.
Map field to sub-query on related entity (Client.balance = Client->orders->sum(total))
yes hasMany()->addField(..aggregate)
Soft-delete
- Easy to implement through conditions. See docs.
Guarded / Fillable properties
- Conditions and OnlyFields do same thing differently.
Romans Malinovskis on Oct. 19^th 2016 12:14:16 AM
Dependencies
Minimal: 2 packages: DSQL Query Builder (http://git.io/dsql)
Global Auditing
yes http://www.agiletoolkit.org/data/extensions/audit
Date of creation, modification
- No but easy to add through hook.
User/IP creation, modification
- Easy to add through a hook.
Reactive actions
AuditLog can be enabled for all models associated with a specific persistence. No further changes are necessary. Works out of the box.
Override, Add fields to audit log
Record dirty fields before persisting. Type-cast into JSON string and store in a single field of AuditLog Model. This model can be persisted anywhere, table, file, etc.
Store old/new field values
yes Yes in JSON and user-readable string.
Revert action (undo) and replay (redo)
yes
Re-do apply action
- Planned
Custom events
yes
Custom fields, table
yes Remove default fields, use your own table, fields, formats.
Store log in any persistence
- Planned
Access to record-specific history
yes $item->ref('AuditLog');
Store incremental revisions
- Easy to add through a hook
If record loaded several times, changing one affects another?
no No
Save only sends dirty fields
yes
Romans Malinovskis on Oct. 18^th 2016 11:46:14 PM
Many-to-Many
yes $user->addCondition('vip', true)->ref('Orders');
Deep Many-to-Many traversal.
yes $user->ref('Orders')->ref('Payments')->action('count');
Cross-Persistence traversal
yes $user->hasMany('Log', new Log($mongodb));
User-defined criteria
yes callback can return referenced model scope.
Automatically save modified entity
no Anti-pattern
Multi-persistence join
- Planned.
UNION existing models
- Planned
Multi-persistence UNION
no But you can merge raw data
Multi-persistence value linking (current_sensor_value)
- Through 'afterLoad' hook.
Before/After operation
yes
Override standard C,R,U,D operations
yes
Persistence-specific hooks (to modify Query)
yes
User-defined hooks
yes
How schema is defined?
method init() in Model class defines fields, relations, conditions, etc.
Code generation
- Planned.
Can be used in Any Framework
yes Through composer/packagist
Romans Malinovskis on Oct. 18^th 2016 11:26:01 PM
How to invoke db-vendor-specific extensions?
yes Exported (SQL-expressions, MongoDB aggregation, etc)
Array as a persistence
yes CRUD operations supported
RestAPI as a persistence
- Planned
Transparent support for NoSQL
- Supported, but drivers not provided.
Criteria Compliance (new record must match condition)
yes With reloading and rollback
Dynamic criteria
yes $user->addCondition('is_expired', false)
JSON string as a persistence
- In development
Same model, multiple persistences
yes Same class. Different object.
Map Entity to SubQuery
- For read-only models.
User-defined types (e.g. "23 USD")
- In development
MongoDB support
- Planned
Neo4j
- Planned
MemCache
- Planned
Convert Model into Query Object
yes $q = $model->action('select');
ALTER, CREATE query building
yes Addon: http://github.com/atk4/schema
SHOW, DESCRIBE, CALL
- Supported through Expressions or Custom query template
User-defined query template
yes Templates for all queries
UPDATE, DELETE, INSERT query building
yes
REPLACE, TRUNCATE
yes
Raw expression
yes new Expression('any sql')
Nested/Composite Queries/Expressions
yes Expression can be in any part of query
Reference domain-model field in query
yes through Expressionable interface
field, where, order, limit
yes Expressions and Parametric values
options, rollup, partition
- Through custom templates
full support for OR conditions
yes Through Object Composition
Get All Data (2x array)
yes
Bypass persistence mapping
yes action('select')->getAll()
Iterator
yes
Single Column
no
Single Value
- Through action
Single row
yes loadAny
Associative Array (id=>value)
no
Model without primary key
yes All conditions added as "where" clause
Read-only Models
yes loadBy($expression)
Load by other field
yes loadBy('field', $value)
Load by ID
yes load(id)
Lazy/Eager-loading
no Anti-pattern
Eager-loading
no Anti-pattern
Specify fields to load
yes onlyFields()
uses * to load all fields
no Anti-pattern
Use Domain logic in multi-record update
- Supported, but must map fields/values manually.
Admin extends User, adds criteria (is_admin=1)
yes Yes, recommended pattern. "User" class adds condition.
Admin extends User, adds accessible fields
yes Yes, recommended pattern.
Extend model, add Join (Disjoined SubTypes)
yes Yes. Unlimited number of joins.
Extend model change table
yes Yes. Used to tweak 3rd party models.
Model can define relation to other Model
yes References are implemented as Objects
One-to-Many
yes $user->hasMany('Orders', new Order());
One-to-One
yes $order->hasOne('user_id', new User());
Romans Malinovskis on Oct. 18^th 2016 10:36:48 PM
Soft-delete
yes
Domain Model Criteria
yes $m->addCondition('gender','M')
Expression-based condition
yes $m->addCondition($m->expr('..'));
PDO Support
yes MySQL, SQLite, Others
Transparent support for NoSQL
yes Native Support
Romans Malinovskis on Oct. 18^th 2016 10:34:20 PM
Dependencies
DSQL Query Builder (http://git.io/dsql)
Minimum PHP Version
5.6
Description
PHP Framework for better Business Logic design and scalable database access
Field Name Mapping
yes PHP: "name" = SQL: "first_name"
Table Name Mapping
yes $model->table = 'my_table'
Map Entity to SubQuery
yes $model->table = $othermodel->action('select')
Map property to expression
yes $model->addExpression()
Map native types (DateTime)
yes $field->type = 'date'
Map field of related Entity ('currency' = currency_id->Model Currency.name)
yes aggregate fields based on "hasMany"
Entity to join multiple tables (adding new record populates both tables)
yes $model->join('other_table')
License
MIT
Latest version
1.1.x
Github / Bitbucket / Sourceforge
http://git.io/ad

Go back to: Agile Data