Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a website, where it loads all data from database and displays it in layout.php.
These data are available to whole project, to all page of that project.
Is loading data from database to layout.php a good idea? Does it make the website loading the first page slower?
Is there any alternative to loading data from database to layout.php?
1) it’s perfectly fine to load data from the database into the layout. If the user needs the data, it’s no different than if you load it on each action/page.
2) Yes, it makes the website loading the first page slower (at least until it’s cached). How much slower varies GREATLY upon the amount of data you’re retrieving and the method you’re retrieving it.
3) If your data is in the database, then no – there’s no alternative than to get it FROM the database. You could look at alternatives for where to store your data, but – with caching, unless you’re talking about a LOT of data, it’s probably not an issue… and if it IS a lot of data, you should probably re-think whether the user really needs that data on all pages.
Additional note:
When you say “where it loads all data from database” – that’s quite a red flag. It’s rarely the case where a user needs ALL the data from the database on any page, let alone EVERY page.