We use cookies to improve your experience. No personal information is gathered and we don't serve ads. Cookies Policy.

ExpressionEngine Logo ExpressionEngine
Features Pricing Support Find A Developer
Partners Upgrades
Blog Add-Ons Learn
Docs Forums University
Log In or Sign Up
Log In Sign Up
ExpressionEngine Logo
Features Pro new Support Find A Developer
Partners Upgrades
Blog Add-Ons Learn
Docs Forums University Blog
  • Home
  • Forums

Update from EE3.5.15 -> EE7.2.2 Didn't break up exp_channel_data table

How Do I?

hypatia's avatar
hypatia
8 posts
3 months ago
hypatia's avatar hypatia

Hi everyone!

I locally updated a client’s site from EE v3.5.15 -> EE v7.2.2, but it didn’t break the exp_channel_data table up into individual tables for each channel field.

I had previously tried to update this client’s site to EE4 years ago, we ran into some problems and ended up reverting, but that update broke up the exp_channel_data table in the way I was expecting this update to do.

One of the critical reasons we’re upgrading is because the exp_channel_data table is so enormous (we have a huge amount of channels and fields), so this is critical for the client.

I downloaded a copy of EE v4.3.8 from GitHub to try and go from v3.5.15->4.3.8, but I’m running into an Exception

SQLSTATE[42S22]: Column not found: 1054 Unknown column 'MemberGroup_member_groups.can_manage_consents' in 'field list'...

I made sure I was pointing at a copy of the EE v3 database, even pulled a new one down and created a new db to be sure, so I’m not sure what to do here.

For the record, the update to EE v7.2.2 went smoothly, it just didn’t break up the exp_channel_data table and that’s critical.

So; does anyone know how to

  • get the v7.2.2 upgrade to break that table up or
  • know which versions of EE v4 I could try to update with/have a link to download that?

Thanks for any help you can offer!

       
Tom Jaeger's avatar
Tom Jaeger
332 posts
3 months ago
Tom Jaeger's avatar Tom Jaeger

Hi Hypatia,

Thanks for getting in touch about this.

I don’t believe EE 4 will break up the channel_data table. However newer versions will go ahead and switch new fields moving forward to the new storage format.

By and large the updater in version 7 has received significant improvements over what was present in version 4, so I would be inclined to stick with that if possible.

Are you currently running into issues with too many columns in that table (or something along those lines?) There might be a few options we can explore.

Thanks,

-Tom Jaeger

       
hypatia's avatar
hypatia
8 posts
3 months ago
hypatia's avatar hypatia

Thanks for the reponse Tom! Yes, we’re running into the too many columns issue. This client has a ton of channels and fields, at this point we’re running into some instability issues and we’re not able to add any new fields.

I actually opened up a support ticket for this. I forgot that there was an addon written for EE4 that would migrate the channel data so each field has its own table. I’m working on it with Robin now.

Running into an sql exception when trying to upgrade from EE v3.5.15 -> 4.3.8, going to try and get that sorted. I’d like to upgrade to EE4 first, split the data out into individual tables, and then upgrade to EE7 from there.

We’ll see how it goes!

👍 1
       

Reply

Sign In To Reply

ExpressionEngine Home Features Pro Contact Version Support
Learn Docs University Forums
Resources Support Add-Ons Partners Blog
Privacy Terms Trademark Use License

Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.