[Deploying Sakai] Migrate Sakai 2.5.0 to 2.6.0

[Jean-Francois Leveque]

Hi Leo and Steve,

 >>>     gmt_context_association
 >>>      gmt_*
 >>>
 >>>

contrib 
(http://confluence.sakaiproject.org/display/GM/Goal+Management+Tools, 
https://source.sakaiproject.org/contrib/syracuse/gmt/)

 >>>     hibernate_unique_key

Hibernate internal, I think.

 >>>     rsn_osp_*
 >>>     rsn_to_*
 >>>     rsn_tool_*

See rSmart 
(http://confluence.sakaiproject.org/display/USER/Making+a+Worksite+Public+(Detailed+Instructions))


J-F

Steve Swinsburg a écrit :
> Hi Leo,
> 
> Comments inline:
> 
>>>     blogger_file
>>>      blogger_image
>>>      blogger_post
>>>
> 
> 
> These will be created when the tool is first accessed so are in 2.6.0
> 
>>>     chat_channel
>>>      chat_message
>>>
> These have been replaced by:
> chat2_channel
> chat2_message
> 
> If you don't have a chat2_* tables, something is wrong. These tables 
> were added for 2.4.
> 
>>>      clemembership
>>>
> Custom/Contrib
> 
>>>     dp_datapoint
>>>      dp_datapoint_submission
>>>      dp_submitter_role
>>>
> Custom/Contrib
> 
>>>     dw_asn_assignment
>>>      dw_asn_att
>>>      dw_asn_*
>>>      dw_form_data_evaluation
>>>      dw_form_evaluation_levels
>>>      dw_gmt_*
>>>
> Related to the rest of the dw_ tables for the Data Warehouse tool. Not 
> seen in 2.6.
> 
>>>      edia_skinmanager_archive
>>>
> EDIA Skin Manager tool, contrib.
> 
>>>     gmt_context_association
>>>      gmt_*
>>>      
>>>
> Custom/Contrib?
> 
>>>     hibernate_unique_key
>>>
> Unknown.
> 
>>>     hierarchy_node
>>>      hierarchy_node_meta
>>>
> Custom/Contrib
> 
>>>     (JForum)
>>>      jforum_*
>>>
> JForum contrib tool
> 
>>>     (Melete)
>>>      melete_*
>>>
> Melete contrib tool
> 
>>>     rsn_osp_*
>>>     rsn_to_*
>>>     rsn_tool_*
>>>
> Unknown.
> 
>>>     sst_events
>>>      sst_job_run
>>>      sst_preferences
>>>      sst_resources
>>>      sst_siteactivity
>>>      sst_sitevisits
>>>
> 
> SiteStats, contrib for 2.6, core for 2.7+
> 
> 
> cheers,
> Steve
> 
> 
> On 24/03/2010, at 12:35 AM, leonardo jr escorido wrote:
> 
>>>     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
>>>     <x-msg://32/mc/compose?to=steve.swinsburg@gmail.com>>/* wrote:
>>>
>>>
>>>         From: Steve Swinsburg <steve.swinsburg at gmail.com
>>>         <x-msg://32/mc/compose?to=steve.swinsburg@gmail.com>>
>>>         Subject: Re: [Deploying Sakai] Migrate Sakai 2.5.0 to 2.6.0
>>>         To: "leonardo jr escorido" <escorido at yahoo.com
>>>         <x-msg://32/mc/compose?to=escorido@yahoo.com>>
>>>         Cc: production at collab.sakaiproject.org
>>>         <x-msg://32/mc/compose?to=production@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.
>>>
>>>         cheers
>>>         Steve