|
When I create PHP projects, is it better to put all database (e.g. MySql) queries in a single file (i.e. "queries.php")? Or is it better to place the respective queries in any "model" classes (i.e. User.php) that I may be creating? Is it bad practice to put database queries anywhere in any PHP file? In the queries.php I would be placing functions for calling the queries. |
|||
|
|
|
I'll leave whats 'bad practice' to the bloggers to fight over. I personally keep queries within the business-logic objects. So yes, User, Order, Sale, etc. I'd find it very inconvenient if they they were all in a separate file. That would be unnecessary added complexity and frankly kind of annoying to have to keep referring back to the file. If for some reason you are worried about finding queries across multiple files, |
|||||||||||||
|
|
Usually, it boils down to choice, when I work with MVC, I tend to keep separate files for all my database objects other than that I've all my database objects/model within a single file. MVC favours the idea of separation,separate models, views and controllers from each other. Over the years i've experienced a growing pattern where individual models are kept in separate files. You can check Ext Js 4 mvc application for reference. I've adopted this same pattern for most of my MVC based application, locating files for editing have never been easier than this and I know where exactly to find which file. New Programmers were also able to work with the codebase, they just knew where to find what. When not using MVC, I tend to have all my models within a single file to avoid the overhead of importing/including these files when needed. For a bigger codebase, sticking with MVC and keeping separate files will help when it comes to maintenance and for a smaller codebase, a single file will suffice. |
|||||
|
|
You can create a base Model which will have the general queries and other models can be inherited from the base model and will contain specific queries to that model. |
|||||||||
|
