We're creating a substantial PHP web application while using Zend framework.

At this time around, the merchandise is beginning to stabilize and that we are leaving quick-and-dirty configurations to be able to avoid regressions. Particularly, we're now focusing on top of merely one shared database that everybody edits. You want to eliminate this As soon as possible.

The Zend framework doesn't appear to aid the classic Radical (Djangoish) mechanism in which you define your computer data models after which it produces the tables for you personally. Therefore we are thinking about utilizing an exterior ORM tool that is going to do this.

We're able to have our schemas and initial fittings defined in plain SQL but this can be a) verbose b) error prone c) lacking level and d) problematic because we should maintain different versions for each supported database after sales.

Therefore we are thinking about utilizing an ORM like Doctrine or Propel to define our models and make tables using their initial data while using selected framework's dialect. The applying uses the Zend tool for ORMing so consistency between both tools would need to be maintained by hand, consider changes tend to be more gradual this does not appear like a problem.

So, far, we're evaluating Doctrine and Propel with this task. Any information on other ORMs that people skipped? Perhaps a different approach altogether for that task at hands?



I really like RedBean. You retain your database models in pure php also it monitors everything.

RedBeanPHP is definitely an free ORM tool for PHP. It concentrates on simplicity and simplicity of use. Why is RedBean unique is it produces your database schema on-the-fly. It scans your computer data and changes the column types to suit your object qualities. In case your models are stable you are able to freeze the database. By doing this RedBean is simple to develop with but can also be very fast on production servers.

Since I have found this ORM, I do not use doctrine anymore.