The biggest OMG when you look at Drupal 7's db at first is: "why there are so many tables?". There were lots of debates regarding Drupal db schema, but if backdrop's target is small to mid projects and better performance, there should be a movement towards getting rid of current "table per field" approach.
There can be something similar to Drupal 6 CCK approach: table per bundle and if field is multivalued it lives in a separate table. There was a project called "PBS" (https://drupal.org/project/pbs) that tried to accomplish that goal but it didn't work out for some reasons.
So what do you things about such a feature?
Recent comments
The simple way is - View source code - Copy and paste what you need - Bold can be easily added with <b> or <strong> tags
Use text editors in Summary Field
I have had a read of what Lando provides, and it's an excellent development tool, and it would solve the problem. But, I would prefer to find out why the problem is there in the first...
How often is the settings.php loaded.
Thanks for the info. I will give it a try...
How often is the settings.php loaded.