2017 © Pedro Peláez
 

library jelly

image

smgladkovskiy/jelly

  • Thursday, August 2, 2018
  • by smgladkovskiy
  • Repository
  • 1 Watchers
  • 0 Stars
  • 34 Installations
  • PHP
  • 0 Dependents
  • 0 Suggesters
  • 37 Forks
  • 0 Open issues
  • 12 Versions
  • 0 % Grown

The README.md

Jelly is a nice little ORM for Kohana 3.1+. The project was originally started by Jonathan Geiger and co-developed by Paul Banks., (*1)

IMPORTANT

Critical to know:, (*2)

  • use the 3.x/master branches for production as the 3.x/develop branches are subject to frequent and major changes
  • userguide is being updated

Requirements, (*3)

Jelly requires the following Kohana versions per Git branch:, (*4)

  • 3.1/develop and 3.1/master branches: Kohana 3.1.3+
  • 3.2/develop and 3.2/master branches: Kohana 3.2+

Useful stuff:, (*5)

Get involved in Jelly's developement, (*6)

As Jelly has always been a community project it's development and future depends on people who are willing to put some time into it. The easiest way to contribute is to fork the project., (*7)

Remember:, (*8)

  • you can directly edit files on GitHub (look for the Edit this file button), there's no need to get familiar with Git if you don't want to
  • please follow the Kohana conventions for coding
  • read the introduction to the unit tests in the guide and run them if you make changes to Jelly to minimalize the chances of introducing new bugs
  • and thanks for helping Jelly become better!

Notable Features

  • Standard support for all of the common relationships — This includes belongs_to, has_many, and many_to_many. Pretty much standard these days., (*9)

  • Top-to-bottom table column aliasing – All references to database columns and tables are made via their aliased names and converted transparently, on the fly., (*10)

  • Active testing on MySQL and SQLite — All of the Jelly unit tests work 100% correctly on both MySQL, SQLite and PostgresSQL databases., (*11)

  • A built-in query builder — This features is a near direct port from Kohana's native ORM. I find its usage much simpler than Sprig's., (*12)

  • Extensible field architecture — All fields in a model are represented by a Field_* class, which can be easily overridden and created for custom needs. Additionally, fields can implement behaviors that let the model know it has special ways of doing things., (*13)

  • No circular references — Fields are well-designed to prevent the infinite loop problem that sometimes plagues Sprig. It's even possible to have same-table child/parent references out of the box without intermediate models., (*14)

The Versions

02/08 2018

dev-3.2/develop

dev-3.2/develop

  Sources   Download

02/08 2018

dev-3.2/master

dev-3.2/master

  Sources   Download

02/08 2018

dev-3.3/develop

dev-3.3/develop

  Sources   Download

02/08 2018

dev-3.1/develop

dev-3.1/develop

  Sources   Download

02/08 2018

dev-3.1/master

dev-3.1/master

  Sources   Download

06/03 2018

v3.0.0

3.0.0.0

  Sources   Download

06/03 2018

1.0

1.0.0.0

  Sources   Download

06/03 2018

1.0.1

1.0.1.0

  Sources   Download

06/03 2018

1.1

1.1.0.0

  Sources   Download

02/06 2016

dev-3.3/master

dev-3.3/master

A flexible ORM for Kohana 3.1+

  Sources   Download

The Requires

 

by jonathangeiger

02/01 2015

3.1.1

3.1.1.0

A flexible ORM for Kohana 3.1+

  Sources   Download

The Requires

 

by jonathangeiger

02/01 2015

3.1.0

3.1.0.0

A flexible ORM for Kohana 3.1+

  Sources   Download

by jonathangeiger