Get Ready For Propel 1.6: The Beta 1 Is Released.
Propel 1.6 has been in development for several months, and yet it has always been ready for real life use. Each added feature is backwards compatible, unit tested, and documented. But until now, only a handfull of developers dared to install it due to its “under development” status.
Guess what? Propel 1.6 is now in beta state. This means that most of the features of the final 1.6 are already there, and that it’s almost ready for your production application. It also means that we need more feedback from beta testers to help us find and fix the last bugs before a stable release that should come within a couple months.
And to motivate you to upgrade, here is a brief list of highlights from the 1.6 version:
- Migrations
- Versionable Behavior
- I18n Behavior
- XML/YAML/JSON/CSV Parsing and Dumping
- Support For SQL Schemas
- Advanced Column Types (ENUM, OBJECT, ARRAY)
The updated Propel 1.6 documentation offers a more detailed list of new features in Propel 1.6.
To upgrade, use your favorite distribution:
Subversion tag
> svn checkout http://svn.propelorm.org/tags/1.6.0BETA1
PEAR
> sudo pear config-set preferred_state beta > sudo pear upgrade propel/propel_generator > sudo pear upgrade propel/propel_runtime
Download
- http://files.propelorm.org/propel-1.6.0BETA1.tar.gz (Linux)
- http://files.propelorm.org/propel-1.6.0BETA1.zip (Windows)
As usual, don’t forget to rebuild your object model classes using the om task. And don’t hesitate to send us feedback on the developers mailing-list, or by opening tickets on the Propel Trac.
19 comments
Complex join should also be a highlight :)
Power to you Francois!
I have two problem:
form generation give me an error. It tells me that the peer class do not have a "getUniqueColumnNames" method. And in fact the method is not there.
I found a solution posted by you to another user that had a similar problem.
He forgot to put:
propel.behavior.default = symfony,symfony_i18n
in his propel.ini
But I have that line and I get the same error.
Another thing I noticed is that behaviors don't like each other....
On my table I have a nested_set and an i18n behavior. But the nested_set method (like getChildren) are not aware of the translations...and always retrieve the same language. A workaround is to use the query class to retrieve childrens like:
->filterByTreeLeft($root->getTreeLeft(), ModelCriteria::GREATER_THAN)
->filterByTreeRight($root->getTreeRight(), ModelCriteria::LESS_THAN)
but It's not so cool.....
Anyway this is a beta....so it's ok to have some problem. Propel 1.6 is really great!!!!
pear-build.xml doesn't contain dbd2propel target
