Outlet ORM |
[eluser]fgrehm[/eluser]
@bjornbjorn Thanks for posting my reply here @M4rc0 I can't tell you 100% that it is faster and how faster it is. The fact that we use plain PDO and that we are not using reflection makes me believe in it. I know that have a PECL extension that does the hydration using C code but I've never tried it. If anyone is interested in doing this benchmark don't forget to show us the results Regards, -- Fábio Rehm
[eluser]tdktank59[/eluser]
How does this compare to Datamapper OverZelous edition?
[eluser]M4rc0[/eluser]
[quote author="fgrehm" date="1225496579"] I'm actually using the repository pattern but to make things simple, here's a sample usage: Code: class OrderController extends Controller Hi (Olá) Fábio, Could you elaborate your example a little bit further? You gave a great introduction to Outlet, and that is the problem because I'm more interested now (also searching for an ORM) How would the model look like in this "repository" pattern? Is this the same as a "Domain Driven Design" pattern? I'm just trying to imagine the model after you presented the controller
[eluser]Unknown[/eluser]
[quote author="M4rc0" date="1259198194"] How would the model look like in this "repository" pattern? Is this the same as a "Domain Driven Design" pattern? I'm just trying to imagine the model after you presented the controller [/quote] This is how I would do it. I was taught that all DB calls are done in the model. The controller and views should not have to request anything from the DB. Might not be the best way, but it works for me. Code: class OrderController extends Controller |
Welcome Guest, Not a member yet? Register Sign In |