Download the PHP package renanbritz/doctrine-utils without Composer
On this page you can find all versions of the php package renanbritz/doctrine-utils. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download renanbritz/doctrine-utils
More information about renanbritz/doctrine-utils
Files in renanbritz/doctrine-utils
Package doctrine-utils
Short Description Helpers to improve productivity with Doctrine ORM.
License MIT
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 doctrine-utils
Doctrine-Utils
Introduction
This project aims to provide a simple interface to query and persist data with Doctrine ORM. It will allow you to focus on domain logic rather than persistence logic, resulting in more readable and dry controllers.
Persistence
By following a few simple conventions you'll be able to reduce the amount of code needed to store and update data to your database when using Doctrine ORM. See examples below.
Examples
Persisting Data (Create and Update Person)
Person POST Data Example
Response Data Example
How it works
The persistence class will recursively persist data to the entity and its associations using the Class Metadata definitions.
Be Careful!
All data passed to the persist() method must have been validated and checked for mass assignment. This library will not help you with that.
Conventions
- The entity identifier must be named
id. - All entity fields and associations must have getter and setter methods formatted in
camelCase. e.g:getName(). Setter method foridis not required. - When updating Collection Associations (One to Many or Many to Many), you must provide the id of elements that you want to keep. Otherwise they will be deleted. If you provide
idalong with other data, the entity will be kept and also persisted again.
