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?
GitHub Issue #:
56
Recent comments
Hi ian, so, in your case all the other admin pages work fine, including the status page, only admin/reports/updates fails? But you can access admin/reports? Weird... I...
Update Report thows "Access denied You are not authorized to access this page."
The File (Field) Paths module should be able to move existing files. I've not tested it, but the module description says: Retroactive updates - rename and/or move...
Moving from /files into subdirectories
Yes indeed. We are exploring a few other more costly options, but as we are a low-resource start-up, we could save a lot of money by integrating Backdrop, CiviCRM and Ubercart for our membership...
UberPOS for Backdrop?