I'm upgrading a site from D5 to D6. My videos are playing fine but I noticed that I'm getting a lot of log entries like:

Message Table footy.video_upload doesn't exist query: SELECT fid FROM video_upload WHERE nid = 2739 in /etc/drupal/all/modules/video/types/video_upload/video_upload.module on line 313.

I don't see anything video module related listed in update.php.

Is there any way to force video_upload_schema to run?

Comments

hypertext200’s picture

hypertext200
he/him
Primary language Singhalese
Location New York City
commented

Please create table called, video_upload and migrate all your D5's file_revision table data into it

bkat’s picture

bkat commented

Just to make sure I did this correctly. I got the table created 

mysql> desc video_upload;
+-------+------------------+------+-----+---------+-------+
| Field | Type             | Null | Key | Default | Extra |
+-------+------------------+------+-----+---------+-------+
| vid   | int(10) unsigned | NO   | PRI | 0       |       |
| nid   | int(10) unsigned | NO   | MUL | 0       |       |
| fid   | int(10) unsigned | NO   | MUL | 0       |       |
+-------+------------------+------+-----+---------+-------+
3 rows in set (0.00 sec)

Importing the D5 data is relatively straightforward except that D5's file_revision table had multiple rows with the same vid.

select fr.vid, v.nid, fr.fid from file_revisions fr, video v, files where fr.vid = v.vid and fr.fid = files.fid order by v.vid, fr.fid;

Here's a sample for one video

| 2739 | 2739 | 16080 |
| 2739 | 2739 | 16091

it looks like 16080 is the video_fid and 16091 is the encoded_video_fid of the video's serialized data. So I set up the video_upload row with the video_fid (16080).

Is that correct?

hypertext200’s picture

hypertext200
he/him
Primary language Singhalese
Location New York City
commented
Status: Active » Fixed

Exactly correct, I'm quite busy these days, your welcome to share your upgrade process here, cause it will useful to many other people

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.