Accidentally truncated yout kaltura.entry table?

Fear not!, for you can rebuild it with this SQL statement:

INSERT INTO kaltura.entry (id, kshow_id, kuser_id, name, type, media_type, data,
thumbnail, views, votes, comments, favorites, total_rank, rank, tags, anonymous,
status, source, source_id, source_link, license_type, credit, length_in_msecs,
partner_id, group_id, int_id, subp_id, display_in_search, puser_id, plays,
permissions, partner_data, access_control_id, conversion_profile_id, categories,
categories_ids, created_at) SELECT de.entry_id, de.kshow_id, de.kuser_id, de.entry_name,
de.entry_type_id, de.entry_media_type_id, de.data, de.thumbnail, de.views, de.votes,
de.comments, de.favorites, de.total_rank, de.rank, de.tags, de.anonymous,
de.entry_status_id, de.entry_media_source_id, de.entry_source_id, de.source_link,
de.entry_license_type_id, de.credit, de.length_in_msecs, de.partner_id, de.group_id,
de.int_id, de.subp_id, de.display_in_search, de.puser_id, de.plays, de.permissions,
de.partner_data, de.access_control_id, de.conversion_profile_id, de.categories,
de.categories_ids, de.created_at FROM kalturadw.dwh_dim_entries AS de;
:)
Of course, we won’t go into how exactly that happened… And you lose some of the metadata, but neh. You get all the important data back without any problems whatsoever. :)
Just remember to bounce and re-index Sphinx afterwards!
October 28, 2011 • Tags: , , • Posted in: Computers

Leave a Reply