The news has just hit the Propel home page: Propel long-awaited 1.3 version was released yesterday.

Not only is Propel 1.3 a lot faster than the previous version (thanks to PDO), it also fixes a handful of problems many of us had with Propel 1.2, and adds a few features as well. Here is a quick overview of interesting changes for symfony users:

• Table and column identifiers are now quoted with ticks in generated SQL code
• Ability to define your own method names for foreign key getters and setters (refPhpName)
• Using clearSelectColumns() and addAsColumn() works
• Fully functional doCount(), handling limit/offset, group by columns, etc.
• Ability to define the primary key of a new object being inserted
• Subsequent calls to retrieveByPK() or doSelect*() with the same parameters return the same object instances (a.k.a. “Object Instance Pooling”)
• Hangling of Master-Slave connections in a replicated environment
• One-to-one relationships
• Native nested sets implementation (no need for sfPropelActAsNestedSetBehaviorPlugin anymore)
• doSelectJoinXXX() methods now default to a left join instead of an inner join
• Ability to self-reference several times AND hydrate related objects

You can check the list of the 242 tickets fixed for this release in the Propel Trac.

It seems that Propel 1.3 will be the default Propel version for symfony 1.2 - Dustin just made the change this morning.

This is great news indeed, and it means that future applications built with symfony and Propel will be even faster and easier to build than the ones we currently know!

Possibly related posts (automatically generated):

• Propel is not hard anymore
• Finding “Augmented” Propel Objects
• sfPropelFinder becomes DbFinder - Announcing 1.0 release
• Comparing Propel, Doctrine and sfPropelFinder