nice, short and sweet article. I think it would be tremendously more useful if you include in some ways this feature can be used to optimise or ease development when we are developing a large application (maybe like a shopping site?) and we have multiple entities in out Db like users, products, product_types, roles, permissions etc. There entities are queried many many times by APIs in different ways. Is there some way we can design these procedures that can help multiple developers working on the application utilise such methods instead of writing their own and increase code duplicity?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
nice, short and sweet article. I think it would be tremendously more useful if you include in some ways this feature can be used to optimise or ease development when we are developing a large application (maybe like a shopping site?) and we have multiple entities in out Db like users, products, product_types, roles, permissions etc. There entities are queried many many times by APIs in different ways. Is there some way we can design these procedures that can help multiple developers working on the application utilise such methods instead of writing their own and increase code duplicity?