Column missing in table: recordings_deleted

Column missing in table: recordings_deleted

by Steve Brisco -
Number of replies: 4
I recently upgraded Moodle from 4.1 to 4.2 and that seems to have gone well.  I am new to this server, which I inherited and am learning as I go.

I noticed that in the Performance Overview, there is an error for Database schema check.  Further investigation shows that for bigbluebuttonbn (I am assuming that this is the table) that column 'recordings_deleted' is missing.



I cloned my VM and then in the clone, uninstalled and then reinstalled the BigBlueButton plugin.  The schema error disappeared in the Performance Overview.  Comparing the differences in the table bigbluebuttonbn on the production database vs. my clone shows that column 'recordings_deleted' has been added to the table.  It seems that all the other column schemas are the same.

running the command show create table mdl_bigbluebuttonbn;   shows the following column in my clone vm and is missing in production:

 `recordings_deleted` tinyint(1) NOT NULL DEFAULT '1',

Am I safe to insert this column into the the production server database table, inserting it in the same column order as on my cloned database?  I intend to use the following command:  

ALTER TABLE mdl_bigbluebuttonbn ADD recordings_deleted tinyint(1) NOT NULL DEFAULT '1' AFTER recordings_html;

Of course I will backup my database before I continue.

Thank you for anyone's feedback.
Average of ratings: -
In reply to Steve Brisco

Re: Column missing in table: recordings_deleted

by Shamiso Jaravaza -
Hi Steve Brisco,

My guess would be that this is related to this issue https://tracker.moodle.org/browse/MDL-74555 (long story short, recordings_deleted was removed in BBB plugin v3.0 but not yet in the core BBB plugin). That is likely why when you uninstalled the plugin then reinstalled it in your VM, there was no longer an error.
In reply to Shamiso Jaravaza

Re: Column missing in table: recordings_deleted

by Steve Brisco -
Thank you Shamiso Jaravaza for some possible backstory.

The deed of inserting the missing column into the database schema was performed 3 weeks ago with no apparent issue.
In reply to Shamiso Jaravaza

Re: Column missing in table: recordings_deleted

by Séverin TERRIER -
Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Testers Picture of Translators
Hi,

I come here after seing, in some of my Moodle sites, using Moodle 4.0 for the moment, but upgraded lately to this version, the same problem when i check database schema.

Other Moodle sites, upgraded sooner to 4.0 (and then 4.1) don't suffer this problem.

If i understand well you explaination, it's because they didn't upgraded to non standard plugin v3.0 (thus deleting this column) before going to Moodle 4.0 ?

In fact, when looking the details of this table, in Moodle 4.0 upgraded later (after using non standard 3.0 i think), i have theses columns :
lockonjoin
lockonjoinconfigurable
And at the opposite, in Moodle 4.0 upgraded sooner, i have the following columns existing (not in Moodle upgraded later) :
recordings_deleted
And, in Moodle version 4.0 upgraded sooner, and then using 4.1, i have the following columns existing (not in Moodle upgraded later) :
recordings_deleted
guestallowed
mustapproveuser
guestlinkuid
guestpassword
So, should i just ignore this, because this column will be deleted in later Moodle version ? Or should i add it, allowing for a proper deletion in the future ? What about the existing lock columns ?

Séverin
In reply to Séverin TERRIER

Re: Column missing in table: recordings_deleted

by Shamiso Jaravaza -
The issue is essentially that this column does not exist only in v3.0. After an upgrade from this version, that column will trigger a missing error in the performance check. Any fresh install 4.0 onwards won't have this issue.

The behavior of the columns you mentioned besides recording_deleted are all expected. This is supposed to happen as these are related to the improvements and deprecation of features across plugin versions. Nothing needs to be done on your end about them. If you could provide the specific Moodle versions you have made these observations on that would help confirm it.