Alex Tech Adventures The webs best tutorials!

** This thread discusses the content article: DataMapper pattern with Zend Framework **

Hello Alex,

It's really good to see you again after a long long days...
Thank you. It's very helpful.

Like Beregu said: Really cool to see another video, will be watching it today.

Still hoping you'll do the tutorial about error handling though..

Thanks!

Epic video!
I have a doubt, is this patter as a whole also called ActiveRecord or what is the difference? anyone?

Just fully watched the video, quite a good one. Will make some adjustments to my mappers. Overall they look quite the same though.

Although it all works in this example, in my case I would consider not creating objects for everything. Sometimes it just isn't needed. It saves a lot of memory..

One problem i ran into btw is the fact that two people might be working on the same data in the database at the same time (person A opens the data for editting in a form, same does person B. Person B updates it after which person A does. This creates a problem in data consitency. Seems to be a problem of the fact that php is stateless..

@vlopez: ActiveRecord is a different pattern. The datamapper (which is a better one to my opinion) creates a bridge between the database and the domain object model. It solves the problem of the difference between the way databases work (most databases at least) and object work.

Active record is best used for simple systems. The idea behind it is that it creates a direct relation between a domain object and a certain row in the database.

@alex: In my system I also use an Identity map next to the datamapper, it makes sure that there is only one instance each domain object model. Might be interesting for you to have a look at.

Yorian,

"One problem i ran into btw is the fact that two people might be working on the same data in the database at the same time (person A opens the data for editting in a form, same does person B. Person B updates it after which person A does. This creates a problem in data consitency. Seems to be a problem of the fact that php is stateless.."

I don't understand, are you saying that when the data is inserted into the DB it the application may confuse userId's recording a comment for example under another users ID? That sounds like a uber problem! Unless you mean something totally different by 'data consistency'.

Could you let me know exactly what the problem is? I'm new to OOP/MVC/ZEND I have designed my DataMapper for my latest project based on this article and the last thing i need is a problem like that. lol

Thank you