Doctrine 2.0.0-ALPHA3 Released

I'll start to use this alpha asap (not in production obviously).

Hey Jwage thanks for this great project,

I just want you to ask how I18n is implemented in D2.0 I liked the way it was in version 1.2, but i dont know how to create a reusable way for I18n without behaviours.

best regards

Well - after a lot of research, I have stumbled upon Doctrine 2.

I have graduated IT science, especially modeling and patterns, and I have to say, Doctrine 2 is all what ORM should be.

Currently, I am on develop of a very complex project, and my team intend to use Doctrine 2 in production (stupid decision, isn't? :-) ). We have all agreed that Doctrine 1.2 will be stabile, but not good in terms of good practice of development, especially of extensible web app.

During development, we will for shore, find problems, bugs or some kind of ideas, and for that, we would like to contribute.

We saw Jira, and in Jira there is portion dedicated only to Doctrine 2. Unfortunately, a lot is shared trough groups, and there is no distinction between Doctrine 2 and other releases.

We suggest, in terms of our productivity, and hopefully yours, to create groups only for Doctrine 2. In that way, users and developers that does not want to have anything with Doctrine 1.+, like us (please do not take this offensively), could exchange info regarding only in what they interested for.

Regarding Doctrine 2 -> Great job! We can not wait for stabile, complete version. This is truly an excellent framework. We are impressed with framework model, used paradigms and patterns. We already start to migrate our current ORM solution to Doctrine 2 and there are benefits already.

All the best and keep up with good work, TheCelavi

I understand why you would want to do that, but I don't think it is a good idea to divide the community. A better alternative would be to post messages with some kind of format. An example subject for Doctrine 2 could be something the following:

Subject: "[doctrine-user] D2: Need help with blah blah"

Now in your e-mail client(gmail is good for this), you can create a filter to only show you the ones you want.

We plan to write a 2.0 I18n extension before Doctrine 2 stable is released. It will be different than Doctrine 1 but still very easy and powerful. It will just be implemented and used/setup a little different. Some things like automatically adding fields to your models requires that the user add the property to the entity class. We can help automate this with code generation but right now we're not focusing on those types of things. We'll start some of the extensions once we get closer to a 2.0 stable release date.

Fine, that reasoning is good. Now only thing to do is to kindly ask from everyone to follow mentioned rule. Is that possible?

Thank you in advance.

Best regards, TheCelavi

I’m member of a development team that is a planning stage of a governmental software. It will have a few thousand of users. We suppose a few month of development for a betha version, and several month before a RC. I come from java world, and especially in the last time, grails. The team have knowledge of php, so I investigate an decide to use Symfony 1.4. While doctrine 1.2 seems a good product, doctrine 2.0 seems even more excellent. The coding stage begins in a month. I would like to use the 2.0 version instead of 1.2, do you think that it will be a good option?. Take in note, that the application will be in production in july 2010. Thanks you.

I think using 2.0 will be fine. It might require a little more work keeping up with the changes we make but it shouldn't be too difficult.

Thanks I will use it!!

Good day!

How about the trees and versioning support similar to 1.2? When can we expect it?

Thanks for your work!

I dream to be able to combine versioning, trees and class table inheritance together.

Thanks again.

As far as trees are concerned, adjancency lists are easy to build. Something like nested sets will not be part of Doctrine 2 itself but will be built as a reuseable extension.

Concerning versioning I'm not sure what you want. If you mean D1 Versionable behavior that will also be an extension.

But Doctrine 2 has built-in versioning for the purpose of optimistic locking. Extremely useful. Check it out here:

http://www.doctrine-project.org/documentation/manual/2_0/en/transactions-and-concurrency#optimistic-locking

The manual is still a bit sparse abotu that topic... sorry for that.

Thank you for your reply.

In our project objects are located in the tree, as in any LDAP catalog. So I dream of supporting operations with the trees from the ORM.

I also want to have a built-in support for versioning as the behavior in the 1.2 version, which we use for full log of objects, as in Wikipedia.

Could you tell when these extensions will be available.

Thanks for good work.

when can we expect 2.0 release?

i mean stable release...