[Deploying Sakai] Migrate Sakai 2.5.0 to 2.6.0

[leonardo jr escorido]

These are the tables in the customized Sakai not found in 2.6.0. I didn't put here all the table names. I think the contrib used can be recognized by their initials. My concern is the "clemembership" table, perhaps this table is being used by the class(es) created by the third party.
 

blogger_file
 blogger_image
 blogger_post

 chat_channel
 chat_message
 
 clemembership

 dp_datapoint
 dp_datapoint_submission
 dp_submitter_role

 dw_asn_assignment
 dw_asn_att
 dw_asn_*
 dw_form_data_evaluation
 dw_form_evaluation_levels
 dw_gmt_*
 
 edia_skinmanager_archive

 gmt_context_association
 gmt_*
 
 hibernate_unique_key
 
 hierarchy_node
 hierarchy_node_meta
 
(JForum)
 jforum_*

(Melete)
 melete_*

rsn_osp_*
 rsn_to_*
 rsn_tool_*
 
(SiteStats ? )
 sst_events
 sst_job_run
 sst_preferences
 sst_resources
 sst_siteactivity
 sst_sitevisits

Thanks,
Leo
--- On Tue, 3/23/10, Steve Swinsburg
 <steve.swinsburg at gmail.com> wrote:

From: Steve Swinsburg <steve.swinsburg at gmail.com>
Subject: Re: [Deploying Sakai] Migrate Sakai 2.5.0 to 2.6.0
To: "leonardo jr escorido" <escorido at yahoo.com>
Cc: production at collab.sakaiproject.org
Date: Tuesday, March 23, 2010, 1:18 AM

Hi Leo,
What are the tables and we can point you in the right direction for the contrib tools you might need to install to match.
That said, you should still be able to apply the conversion to the 2.5 database to bring it up to 2.6 and get it going. Extra tables shouldn't do any harm.
cheersSteve



      



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/production/attachments/20100323/b4295ba9/attachment.html