Jump to content

Issues with the prestashop database design


MikeM.

Recommended Posts

Hi, I already said this before, but now I did another SHOCKING EXPERIENCE.

As a Web Developer myself, I get annoyed that prestashop saves up data multiple times.

However we can get over that, althrough it's not at all necessary and only takes up data.

 

TODAY, just a few seconds ago, I seen something shockingly.

Prestashop it's admin panel logs everything, well that's the good thing.

But wait a minute, it saves "date_add" and "date_upd"

 

You might ask yourself, wow what's the big issue with that?

 

Well a log item NEVER EVER changes.

Log Items are made to show what has been done, not to be edited freely.

This makes the whole column `data_upd` useless!

My boss has a small webshop, which already has a log of 5315 rows.

What does this mean?

Well there are already 5315 items not used at all because of that column...

Which takes up more bytes as you whish.

 

I said it before and will do it again, REDO THE DATABASE DESIGN, there are so many issues with it not following the DB Design Regulations, that it takes up more database space than required.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...