WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #35669, comment 6


Ignore:
Timestamp:
08/18/2016 10:33:15 PM (4 years ago)
Author:
PeterRKnight
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #35669, comment 6

    initial v1  
    88> I think for me the issue is that the wp_posts table is now poorly named and used for stuff it was not originally intended for. (I actually implement my nav menus though code to keep entries out of the database!)
    99
    10 To extend on the reality that the wp_posts table really effectively an alias for wp_objects, if you are a fan of the databases, you should be rejoiced. Currently widgets are stored in the options table, which is not a great fit. Widgets define content after all and most options are autoloaded on every page load. As custom post objects the widgets can take advantage of post type-like features, such as authorship, scheduling, revisions etc.
     10To extend on the reality that the wp_posts table is effectively an alias for wp_objects, if you are a fan of the databases, you should be rejoiced. Currently widgets are stored in the options table, which is not a great fit. Widgets define content after all and most options are autoloaded on every page load. As custom post objects the widgets can take advantage of post type-like features, such as authorship, scheduling, revisions etc.