Compared with other libraries with similar feature sets, Jelly is relatively light-weight yet powerfully extenisble.
All references to database columns and tables are made via their aliased names and converted transparently, on the fly.
Handle models using a familiar, alias-aware API that is cleanly extensible per-model.
All field data handling logic, including relationships is implemented in a
Field_* class, which can be extended
to provide huge flexibility without changes to the core library.
While our primary concern is to get the most important features right and stable, we have designed the API with our future plans in mind, including polymorphism and model behaviors.