Jump to content

Data migration from 1.6 to 1.7 and weight difference between db 1.6 and db 1.7


ballashop
 Share

Recommended Posts

Hi,
we migrated all data from 1.6.1.24 to new 1.7.6.3 by one of migration module into the PS marketplace. We had to do this because the upgrade gave us an infinite number of errors and therefore it was impossible to proceed. So we decided to use a data migration module.

After migration we compare the db between 1.6 and 1.7, there are a lot of different, the 1.6 db weight more than 300 mb while the 1.7 one less than 20 mb, how is it possible? 
When we tried to upgrade by native module 1-Click Upgrade, the 1.7 db weighed like 1.6.

Other different, the db structure. 
For example the ps_access:

1.6
CREATE TABLE IF NOT EXISTS `ps_access` (
  `id_profile` int(10) unsigned NOT NULL,
  `id_tab` int(10) unsigned NOT NULL,
  `view` int(11) NOT NULL,
  `add` int(11) NOT NULL,
  `edit` int(11) NOT NULL,
  `delete` int(11) NOT NULL,
  PRIMARY KEY (`id_profile`,`id_tab`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

1.7
CREATE TABLE IF NOT EXISTS `ps_access` (
  `id_profile` int(10) unsigned NOT NULL,
  `id_authorization_role` int(10) unsigned NOT NULL,
  PRIMARY KEY (`id_profile`,`id_authorization_role`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

Before putting the site into production way, we wanted to ask to the Prestashop community if this is normal.
If you have experience and advice please write.

Thank a lot.

E.

Share this post


Link to post
Share on other sites

11 minutes ago, Knowband Plugins said:

We believe there is no definite answer for the same but if you site is working fine (Test the functionalities after upgrade) & upgrade is having all the previous data like products, orders customers etc then there is no issue.
 

 

Hi @Knowband Plugins what operations do you recommend me to do? 

I mean specifically.

Thanks.

Share this post


Link to post
Share on other sites

Hi @Knowband Plugins

I discovered an important thing, the module we used for migration does not migrate the site visit data, therefore all the statistical data is distorted. I find it incredible that the developer has not considered this option.
Could it depend on some different module of the 1.7 version? 
Can user visit statistics be imported separately?

Thanks a lot for any tips.

Share this post


Link to post
Share on other sites

The developers of the migration modules wrote to me that visitor statistics cannot be migrated with their module.
I ask to myself why we should buy the migration module if we still need to request a dedicated developer job.

Any idea to solve it? Possible that nobody needs to migrate statistical data from 1.6 to 1.7?

Thanks for any suggestion.

Share this post


Link to post
Share on other sites

  • 2 months later...

Important update about data migration!

It is important to know that the migration module cannot migrate loyalty points due to the lack of the 1.7 related module.
Another consideration, even products saved in the customer wish list are likely to get lost during the migration.
These data will have to be migrated separately.
Thanks for any suggestion.

Share this post


Link to post
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
 Share

×
×
  • Create New...

Important Information

Cookies ensure the smooth running of our services. Using these, you accept the use of cookies. Learn More