Re: What's the worst that can happen with below database design? Immediately or in the future?
Posted by: Ozgur Zeren
Date: September 05, 2014 03:27PM

Having worked extensively on big databases running on wordpress and oscommerce separately, i would say that this format is much more closer to oscommerce - which has relational design - than wordpress, which has a hybrid design.

i would summarize this format as 'relational table with generic fields', if a summary was required.

definitely not eav, because ALL the data which will be stored, are stored in their own fields. Ie, field1 varchar for username, field2 varchar for email, field3 timestamp for registration date and so on.

there wont be any

key - data type - data format.

Basically ALL the data which is stored in the database are stored in their own fields properly according to their types.

The fields data_type and attribute_name are just for differentiating in between the data models of different modules - they dont have anything to do with the actual data that is stored in any of the fields.

Options: ReplyQuote




Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.