Best way to work with models/queries in Phalcon?

Since less than two month I in a company that use Phalcon, and the more different thing i see with Symfony is that use Active Record instead of Data Mapper and I'm a bit confuse because i don't know exactly how to do some things.

There, here we go!

There are any way to create "repositories" or something similar? I think that putting the queries and the logic of parsing the results inside the model are a little bit dirty.
It's okay to have the model auto generated by doctrine and if you want to extend make a class that extend this model? Are any way to keep the changes you make to the model?
Where is the correct place to put the queries? and the other methods you need that not are for retrieving data?

I don't know exactly how to work with active record, or what are the good practices of the active record instead of the data mapper.

Thanks for all!

you can seperate them ofc by using the models manager an the query object. i've built a stateless service architecture fir interacting objects but these are design decisions and based on taste.
check the phalcon dev tools for that
since it's an active record concept and you wanna turn it into a data mapper concept the answer is : just name it so it makes sense and think about the structure before you implement it.

i hope this is helping a little :)

Thanks for the info about Model Manager, i understand it's like a repository to make actions with the model?

well not really but you can create a repository like structure using the injection aware interface. like "abstract class repository implements .." and add the di and the modelmanager as properties. so all the child repositories can use the data model and the query object you could use returns the resultset interface which will map the model names to the phql sql abstraction. .... i'm getting to technical :) just check the custom query examples of phalcon :) and the rest is really obvious and easy to implement :)

http://pastebin.com/ML3hpNcM as an example -> just creating a basic repository structure and moving the queries out of the active records. :)

since i know my explainations tend to confuse people :) but the code is pretty obvious and if you download the phalcon dev tools and use a modern ide you get autocomplete for the methods of the classes so you can explore the options. in theory you could implement them with zephir and add a data mapping structure to phalcon :) or you just implement it in php ans share it with the community :)

Thread

Best way to work with models/queries in Phalcon?

Responses(1)

Recent threads

Search Hashnode

Best way to work with models/queries in Phalcon?

Responses(1)

Recent threads