I am still using Propel, and the big drawback of Propel is as said the
cumbersome way to define relations with criteria.
I wrote a Propel helper (that requires a little extension for the
propel builder) that allows you to do joins in propel much easier, see
the sfGridPlugin:
See
Hi
A comparison between LightORM, Propel and Doctrine is given at this link
http://phplightorm.wiki.sourceforge.net/LightOrm+vs+Propel+vs+Doctrine+benchmark
On Tue, Mar 24, 2009 at 6:28 PM, Campezzi campe...@gmail.com wrote:
Hello there,
I've been a PHP developer for some time now, and
Hello,
Couple of reasons why i've chosen Doctrine instead of Propel:
- far, far, far, far better documentation
- IMHO more readable queries with DQL than with criterions
- code is maintained and actively developed - this means that bug will
be fixed and support for new version of dbm's will be
Michal G wrote:
Hello,
Couple of reasons why i've chosen Doctrine instead of Propel:
- far, far, far, far better documentation
- IMHO more readable queries with DQL than with criterions
- code is maintained and actively developed - this means that bug will
be fixed and support for new
Hello everyone,
Thanks for the replies. From what I heard, I'd better take a closer
look into Doctrine before sealing the deal with Propel. At the
moment, I'm inclined to think that working with Propel is a bit more
intuitive (at least it has been easier for me to understand), but I
have already
Just wanted to point out that the benchmark is being done on Doctrine
version 0.10.2. A LOT of work has been done on doctrine since and the
current doctrine included with symfony is 1.0 and the current stable
version of doctrine is 1.1 and much much more stable from the days
0.10.
P.s. No I'm
Propel also has behaviours -- you just have to enable it when you build the
model.
What I find annoying is that whilst methods such as doDelete have multiple
extension points with behaviours the get/set functions have no override
points. This means that common code can't be added without editing
