Kris Wallsmith
Our marathon month of weekly releases continues apace with symfony versions 1.3.0-RC2 and 1.4.0-RC2 available for immediate download. These will be the last releases before stable versions drop next week. As always, if you haven't upgraded a project from 1.2 to 1.3 (or started a new one with 1.4) make it a present to yourself to do so now.
We're getting close to a stable release so I only have a few changes to report here. Checkout the What's New and Upgrade tutorials for more information, or read through the Deprecated report for the dirty details.
DQL on the CLI
The doctrine:dql task got a little love this week. You can now run queries
through this task using PDO-style ? placeholders, passing parameters as
additional arguments. When combined with the new --table option, the
doctrine:dql task is an attractive alternative to the standard database
shell when running queries from the CLI.
Better Backward Compatibility
A few changes were reverted for better backward compatibility with symfony 1.2. Most notably, the common filter is back and will no longer be removed by the project upgrade task. However, new projects will not use the filter as this is the recommended approach.
The symfony team is eager for your feedback as we come into the home stretch for these final two major releases on the 1.x branch.
Que lindo!! Estoy desarrollando un nuevo proyecto y la verdad que me da mucho gusto. Antes hice dos proyectos, uno en symfony 1.1, despues otro en symfony 1.2. Ahora hace un mes en los tiempos libres empece con 1.3 y hace unos minutos actualice a 1.4.0RC2 y la verdad me da nuevas energias. Lo siento mas rapido el framework, la cache es mas inteligente, doctrine 1.2 me gusta mas.
Saludos y felicitaciones equipo de symfony
why task are missing like fix-perms or doctrine:build-all-reload in the svn branch of 1.4 ?
@eljam: These tasks are not missing, merely their aliases were from a symfony 1.0.x time. These aliases have been removed. The doctrine:build command has been revamped. Please read the UPGRADE and WHAT'S NEW documentation of 1.3 for more information.
--Annis
@Annis, ok this is not a problem of aliases from 1.0. When you launch ./symfony you have all the listed task like doctrine :build :build-all :build-all-load with the namespace thing. With my first checkout the build-all command was not listed. I checkout again the 1.4RC2 and all is fine now. I don't if it was a cache or my symlink which was wrong.
Will there be a new 1.4 version of the printed version of "The Definitive Guide to symfony"?
I do not look like some files not found in the SVN repository.
/data/web/sf/sf_web_debug/js
On debug page displays JavaScript erorr. Does it have special meaning? Or a simple mistake?
Fabien You should change routing. Now when we want to pass Doctrine object from view from form to action we mast change routing file and add routing for models. For me Symfony is better than ASP.NET MVC (ASP.NET MVC isn't ASP.NET Web Forms) - but routing is one of the worst things in symfony - You can see ASP.NET MVC overwiew here: http://www.asp.net/learn/mvc/tutorial-21-cs.aspx And here is their routing: http://www.asp.net/learn/mvc/tutorial-05-cs.aspx
In ASP.NET MVC I don't need change routing file to could pass ORM objects from form in view to action.
@dziobacz:
A bit old but these slides explain the new concept (summary is on page 26): http://fabien.potencier.org/talk/16/symfony-camp-2008-REST
Play around with it, use "$this->getRoute()->getObject()" in your actions. Your code gets much nicer, shorter and easier thanks to the tons of new features you get with sf 1.3/1.4 when coming from sf 1.0 :-)
I only have done upgrade from 1.2.9 to 1.4 and compared the speed. It is two times lower than in 1.2.x! This is how it should be? Prooflink: http://www.picamatic.com/show/2009/11/27/04/33/6100324_898x420.PNG
@vatson: You cannot compare numbers from the web debug toolbar for just one request. It does not make any sense. It looks like the cache was empty for symfony 1.4, and not for symfony 1.2 for instance. Performance can only be relevant if done with a production environment and with a proper load test setup.