Download the PHP package rawebone/ormish without Composer
On this page you can find all versions of the php package rawebone/ormish. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download rawebone/ormish
More information about rawebone/ormish
Files in rawebone/ormish
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package ormish
Ormish
Ormish is an Object Relational Mapper with an emphasis on simplicity. It relies on a certain amount of extension and adherence to database conventions. It has one, generic SQL connector at the moment for maximum compatibility.
The library aims to provide an active record pattern to database access, with a basic syntax for general use and an ability to easily extend for your own purposes. I am writing this primarily to learn the Domain and for my own purposes, unless there is significant interest for other parties.
Note: This is a work in progress
Installation
Installation is via Composer:
Usage
The ORM is pretty simple to get to grips with:
The markup for entities is also quite straight forward:
There is a little more boilerplate required for this compared to other systems, but the payoff is that you have a simple mechanism to keep everything in check.
Transactions
By default, operations on the database are not carried out inside of transactions,
however one can achieve this by the use of the Transaction object:
Contributing
Namespaces
The root namespace Rawebone\Ormish is reserved for objects which are directly
visible to the end user (like Database, Table, Entity) for easy use of the API.
The Rawbone\Ormish\Actions namespace is for Actions that can be applied to a
Gateway object (for example: $table->find(1) would refer to a Finder action).
The goal is to create small objects containing the logic required for working
with the database in a clean and simple way.
The Rawebone\Ormish\Utilities namespace is for objects which are consumed
internally in the API and have no outward value to the users. The end user,
for example, does not need to see the Shadow or NullShadow objects to
use the API.
Roadmap
For Version 0.2.0
- Complete implementation of
Actionsand remove this functionality from theGatewayobject. (100%) - Complete move of objects into the
Utilitiesnamespace which have no outward value to end users. (90%) - Change to an Exception model for errors. (100%)
For Version 0.3.0
- Implement a type mapping system. This will be breaking as will it require additional annotations on the Entities.
- Implement annotations for Tables and deprecate attaching tables manually. This will help keep the Entities close to the database.
- Implement
Relationshiphandling in a similar fashion to theActions.
For Version 0.4.0
- Implement caching (hopefully via a PSR) of results and possibly configuration
- Basic schema manipulation
Testing
All tests are being run with PhpSpec.
License
MIT License. Go hog wild.
