The Database structure of WordPress should be rethought if WordPress is going to move to a more and more CMS’s based system. (today’s Award seems that this is indeed the case)
In times of PDO, Doctrine etc. creating a sweet Database layout shouldnt be the biggest issue no more?
Why not update the sql tables names when creating a new page type? i.e. we create a new post/page type titled “cars”…why not create a new database table entitled cars with all default fields in there. Custom fields would simple add a new Field/Column into that table. in this way we would have an extremly clean database design, which other applications can tap into easily as well. This would result in a high performance database layout and offer a great new way to design flexible, scalable applications.
The benefit would be extremely great too all powerusers/cms users etc. and normal “blog” users wouldn’t feel a thing as for them nothing changes.
WordPress doesn’t get bloated, but just more mature.
Using convention over configuration would allows wordpress to tap into existing databases which have an incremental id and use that data instantly. (if the database layout fits a certain style and some additional fields (published, author etc. are added)
give me your thoughts on this please.
- The topic ‘Database structure WordPress’ is closed to new replies.