Doctrine 2 ALPHA4 Released

Tags: release, 2.0, alpha

Posted 6 months ago by romanb

Today we are happy to announce the release of the next, and hopefully last, alpha release of Doctrine 2. With over 60 fixed bugs and some improvements this is another significant step towards the final release.

Highlights

View the complete change log to see a detailed list of every change contained in this release. You can download this release and report any issues you find in Jira.

We would like to thank everyone who participated in this release through bug reports, patches and suggestions.

What is Next?

We are planning to work towards entering beta from here on. There are still some backwards-incompatible changes to come. Once we hit beta, efforts will concentrate on fixing bugs and further stabilizing the code base. The first beta release is currently scheduled for March 1st, 2010.


Comments (14) [ add comment ]

Release Posted by Nami about 6 months ago.

Really great ! :)

Templates Posted by mh about 6 months ago.

Does Doctrine 2 support behaviors/templates as in Doctrine 1 or not yet?

@mh Posted by romanb about 6 months ago.

No, and it never will. Not at all like in Doctrine 1 at least.

"Behaviors", "Templates", etc. are all special constructs for Doctrine 1's intrusive architecture.

With Doctrine 2 you just use "plain old OOP", no special ORM-dependend constructs.

@romanb Posted by Nami about 6 months ago.

Yes, many difference between D1 and D2. I think the reason of no behavior is first the absence of inherit ... And that's what I will never use Doctrine 2.

@Nami Posted by romanb about 6 months ago.

Thats fine. By the way, D1 needs maintainers. If you like it so much, maybe you want to step in and fix some of the myriad of bugs in these fantastic behaviors/templates.

@romanb Posted by Nami about 6 months ago.

Ok, for me Doctrine 1 and Doctrine 2 is two differents things: Doctrine 1 have more flexibility in models, but it's obstrusive. Doctrine 2 need more configuration, but it's flexible totally. So, D1 would be used for creating fast an application, and D2 is useful for create an application with all options configurable.

Ok, when I said "I will never use D2", it was for behaviors. I have some projects on D2 (but find a server with php5.3 is not so easy ...). D2 is a fantastic job, but can't be used in a live site.

Behaviors Posted by Giorgio Sironi about 6 months ago.

Great news. The good part of behaviors implemented in userland code is the independence from the database; maybe frameworks code (such as ZF or Symphony) could help implement the same features that the old behaviors provided.

documentation Posted by Alex about 6 months ago.

In what order does the documentation complete? It's quite thorough already, but the chapter about Custom Repositories (one which I need to complete my Doctrine 2.0 examination).

new features Posted by Michal about 6 months ago.

Hi,

Can someone point me to some document about new features in D2?

I have heard that D2 is cool, but don't know why. I haven't seen any comparison between D1 and D2 that describes new features ie. "you can't do this with doctrine 1, but it's pretty easy with doctrine 2 and you can do this this way".

Anyone have such comparison?

Regards, Michal

re Posted by Guilherme Blanco about 6 months ago.

@Michal http://www.doctrine-project.org/documentation/manual/2_0/en/introduction

@Nami Roman is against intrusive code in Doctrine 2. I agree with him, since it's a can of worms. We fight every day with issues related to behaviors support, and that's why we outsourced it from D2.

The actual point is that behaviors are still possible to be implemented, but it wont be internal. I just finished to plan the Hierarchical support for D2, and I'll start to implement it soon (as soon as I finish a couple of remaining tasks that are already scheduled for me).

We're currently in the process to define which event would we trigger from Doctrine to extensions, as well as how extensions could be treated inside Doctrine structure. A well planned solution takes time, it's not a one night decision.

Cheers,

Today : D1 or D2 Posted by puentesdiaz about 6 months ago.

Hi to all

If we want be serious, which version do you will use/learn?

Today, is important know D1?, or just go directly to D2

Zend_Date Posted by alexey_baranov about 6 months ago.

Hello!

As I know Doctrine 2 has SQL timestamp <-> PHP DateTime as the default type conversation. Can you add SQL timestamp <-> Zend_Date conversation too?

Thanks.

NestedSet in Doctr2 Posted by tester about 3 months ago.

hello, for example we use NestedSet in our project. can we go to Doctrine2, will these behaviors will provide in another way ? or do we have to forget Doctrine2 for a long time ? thank's

the news Posted by tester about 3 months ago.

I must agree, in Doctrine2 documentation there is not a clear document with all differences with Doctrine 1.x, so we can see in a look what will change in our projects

Create Comment