When you install WordPress you need to edit your
wp-config.php file to setup a database connection. If you scroll down further in this file with your favourite text editor you will find a line named
$table_prefix = 'wp_';. This is the prefix for all the tables that get created in the database when WordPress is installed and used.
The prefix is important when using a single database for multiple WordPress’. A different prefix for each instance of WordPress will prevent clashes when saving and serving content from your site.
It is easiest to pick a prefix, or leave the default and be happy with that. However, there are some situations that require the table prefix to be changed.
- You may be consolidating WordPress installations and require a single database to be shared between multiple instances.
- Setting a non-default prefix can add extra security from ‘script kiddies’.
- Maybe your site has changed and the prefix is no longer applicable – it will make it easier to manage your DB with a prefix which reflects the name of your site.
I made some comments about the challenges that arise when hosting databases, in particular production databases, in a cloud environment. It was interesting to consider where the pain points would be with PaaS and IaaS, and the benefits and draw backs of each option.
When executing your organisation’s database strategy it is important to consider whether this will be an IaaS or PaaS implementation. A decision between IaaS and PaaS will generally depend on the type of database and the expertise in the business, according to Joe Gardiner, product head at cloud hosting firm CatN
“IaaS is becoming more and more commoditised so it can appear an inexpensive option. However, the expertise required to configure a scalable and resilient environment on IaaS for a production database are not to be underestimated and are rarely cheap,” says Gardiner.
Taken from the article Databases in the cloud – all you need to know on Cloud Pro.
Some points I made about the importance of good code hosted on the cloud were published on Cloud Pro.
One area that Joe Gardiner, head of product at cloud hosting firm Catn, believes is overlooked is the quality of code used in cloud applications
“Let’s face it – good code is better than poor code – especially if that poor code means you are using much more public cloud capacity than you actually need,” he says. “A good project manager should have regular “sanity check” milestones that should highlight whether there is a way to optimise the resource requirements of an application.
Taken from the article Cloud costs – making sure a move to public IaaS isn’t a financial drain on Cloud Pro.
This is a great article about the self perception of generation Y.
Lucy is part of Generation Y, the generation born between the late 1970s and the mid 1990s. She’s also part of a yuppie culture that makes up a large portion of Gen Y.
I have a term for yuppies in the Gen Y age group — I call them Gen Y Protagonists & Special Yuppies, or GYPSYs. A GYPSY is a unique brand of yuppie, one who thinks they are the main character of a very special story.