Dev Discussions - ActiveRecord, Data Mapper, and Doctrine

preview_player
Показать описание
In this video, we discuss ActiveRecord, Doctrine, Data Mapper, Value Objects, and some other stuff.

Рекомендации по теме
Комментарии
Автор

This discussion was awesome!!! Got me to change to doctrine, all I can say is thank you. In response to the uniqueness conundrum, I've found the Specification Pattern to be quite helpful.



Thanks again Shawn. Believe it or not the Laravel podcast got me into programming. You guys make potentially dry concepts digestible, and as a listener from the beginning your book recommendations, pattern discussions, and guests lead me down a sound research path. Your the man. Peace.

Bear-qsol
Автор

Hey man, you are very good at explaining this concepts and patterns. Keep goinf for it!

FedeOttalagano
Автор

email_email, name_first and name_last nowhere look like a good idea. Because at one point in time I may change the $email field from a primitive value to a value-object and the name in the database will change from email to email_email. Also, even if it looks like "don't care" in theory, in practice you won't find many cases where you really need email_email. It just looks weird and confusing. Why would you need such a field...

More to that, the relationships forced by ActiveRecord would make your code less error prone. Why would you make your objects not correspond to your storages - may you supply a useful example?

anton_adelaide
Автор

Thanks for awesome video, inspite bad sound quality.
Shawn has become my PHP/Laravel hero. I should take a photo with him, not with Taylor Otwell on Laracon this year :) Also, I am moving to Doctrine slowly. There are comments that exchanging Eloquent simplicity for Doctrine (which is far complex to work with) is not really wise idea. I think that one of the reason for Laravel popularity is Eloquent. But I will definitelly join IRC for more discussions.

kokoloism