Jump to content

Welcome, Guest!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

SLiCK_303

core updater database schema

Recommended Posts

I'm wondering if the Database Schema is supposed to work yet or not?  All I get, on every version on tb's I've tried is....

core.PNG

Share this post


Link to post
Share on other sites

Not at the moment.

In fact, most people don't even see this tab. Markus doesn't want this new feature to be available to general audience yet. 

Core updater version with this feature is no longer available for update. And those who updated during the brief time that was available (as you did) can't use this new feature as well. That's because core code was updated to not support database changes detection.

Anyway, if you want to test it, I'd be glad. All you need to do is

  1. forward your code to bleeding edge
  2. add this line to /config/config.inc.php -- as shown in this commit
define('TB_OBJECT_MODELS_AUTHORITATIVE', true);

With this constant, your version of core updater will enable the database schema comparison tool. If you migrated from prestashop, or even if you come from older version of tb, you should see plenty of database differences. Most of them should be benign, though

Share this post


Link to post
Share on other sites

Making that change let it work, thanks.  Sorry I missed that commit, thanks for the link to it.  90% of mine said critical....

Share this post


Link to post
Share on other sites

sure...this is most of it, i fixed a couple of them....  Looks like most of them have to do with price, and rounding I assume.

db1.PNG

db2.PNG

Edited by SLiCK_303

Share this post


Link to post
Share on other sites

How to auto apply all thoses fixes when migrating from a presta 1.5 for example...

If I try to click to fix each line.. it will takes ages ^^ would be nice to apply all fixes in only one click 🙂

 

Share this post


Link to post
Share on other sites

It would, but that functionality is not implemented on purpose - this db migration thingy is still in an early phases, and there can be some bugs. It's much safer to simply not allow 'Fix all', or even 'Automatic fixes' right now

Share this post


Link to post
Share on other sites
1 hour ago, datakick said:

It would, but that functionality is not implemented on purpose - this db migration thingy is still in an early phases, and there can be some bugs. It's much safer to simply not allow 'Fix all', or even 'Automatic fixes' right now

Ok..i unserstand that but i'd like to make it possible for those who'd like to, even with danger !

 

Because now ..it will take me maybe around 2 days clicking all the Time to fix it all..please tell me where to engage all recommandations even it breaks the dB afterwards..i'd like to test it.

Edited by zen

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

×
×
  • Create New...