[Building Sakai] SITEASSOC_CONTEXT_ASSOCIATION and TAGGABLE_LINK
Maurer, Christopher Wayne
chmaurer at iupui.edu
Wed Jul 13 06:50:12 PDT 2011
Autoddl would definitely create it and the lack of migration script is
probably just an oversight. Like I said earlier, I remember it going in
and out of the scripts (during the qa period) based on testing. It could
have been that one of the qa servers had a slightly different
configuration and that one won out in deciding that it stayed out.
Anthony, it sounds like conversion is indeed missing, but where do you
think we should add it?
Chris
On 7/13/11 9:35 AM, "DAVID ROLDAN MARTINEZ" <darolmar at upvnet.upv.es> wrote:
>That's what I did. But I stilll don't understand why the table is not
>automatically created and/or not included on migration scripts.
>
>Thanks a lot for your help!
>
>________________________________________
>De: Maurer, Christopher Wayne [chmaurer at iupui.edu]
>Enviado el: miércoles, 13 de julio de 2011 15:27
>Para: DAVID ROLDAN MARTINEZ; Anthony Whyte
>CC: Developers Sakai-Dev
>Asunto: Re: [Building Sakai] SITEASSOC_CONTEXT_ASSOCIATION and
>TAGGABLE_LINK
>
>Or you could just run the sql by hand...you running oracle?
>If so, this should work:
>
>CREATE TABLE TAGGABLE_LINK (
> LINK_ID VARCHAR2(36) NOT NULL,
> VERSION NUMBER(10,0) NOT NULL,
> ACTIVITY_REF VARCHAR2(255) NOT NULL,
> TAG_CRITERIA_REF VARCHAR2(255) NOT NULL,
> RUBRIC CLOB NULL,
> RATIONALE CLOB NULL,
> EXPORT_STRING NUMBER(10,0) NOT NULL,
> VISIBLE NUMBER(1,0) NOT NULL,
> LOCKED NUMBER(1,0) DEFAULT 0 NULL,
> CONSTRAINT TAGGABLE_LINK_PK PRIMARY KEY(LINK_ID)
>);
>
>
>Chris
>
>On 7/13/11 3:01 AM, "DAVID ROLDAN MARTINEZ" <darolmar at upvnet.upv.es>
>wrote:
>
>>Then, should I restart Sakai with auto.dll set so that TAGGLABLE_LINK
>>will be created?
>>
>>David
>>________________________________________
>>De: Maurer, Christopher Wayne [chmaurer at iupui.edu]
>>Enviado el: martes, 12 de julio de 2011 22:05
>>Para: DAVID ROLDAN MARTINEZ; Anthony Whyte
>>CC: Developers Sakai-Dev
>>Asunto: Re: [Building Sakai] SITEASSOC_CONTEXT_ASSOCIATION and
>>TAGGABLE_LINK
>>
>>It is linked with legacy assignments. Anthony was perhaps speaking a
>>little more historically when he said taggable was removed from
>>assignments. The code used to live in the assignments module but it was
>>pulled out into its own module.
>>
>>Chris
>>
>>On 7/12/11 3:57 PM, "DAVID ROLDAN MARTINEZ" <darolmar at upvnet.upv.es>
>>wrote:
>>
>>>Hmmm....Then I don't understand what can be happening...
>>>
>>>If TAGGLABLE_LINK is not linked with legacy assignments, why our
>>>installation is trying to access that table?
>>>
>>>Any idea?
>>>
>>>Thanks a lot!!
>>>David
>>>________________________________________
>>>De: Anthony Whyte [arwhyte at umich.edu]
>>>Enviado el: martes, 12 de julio de 2011 17:09
>>>Para: DAVID ROLDAN MARTINEZ
>>>CC: Developers Sakai-Dev; Maurer Christopher
>>>Asunto: Re: [Building Sakai] SITEASSOC_CONTEXT_ASSOCIATION and
>>>TAGGABLE_LINK
>>>
>>>There is a hibernate mapping for TAGGABLE_LINK in the taggable project.
>>>It along with the rest of the taggable stuff was removed from
>>>assignments
>>>back in March 2008 (fix version Sakai 2.6.0) according to
>>>https://jira.sakaiproject.org/browse/SAK-13237.
>>>
>>>/taggable/trunk/taggable-hbm/hbm/src/java/org/sakaiproject/taggable/impl
>>>/
>>>L
>>>inkImpl.hbm.xml
>>>
>>>The only explicit reference to TAGGABLE_LINK in a *.sql conversion
>>>script
>>>involves a test script for assignment2. See
>>>assignment2/selenium-test/sakaitrunk-db.sql.
>>>
>>>Cheers,
>>>
>>>Anthony
>>>
>>>--
>>>-- Table structure for table `TAGGABLE_LINK`
>>>--
>>>
>>>DROP TABLE IF EXISTS `TAGGABLE_LINK`;
>>>/*!40101 SET @saved_cs_client = @@character_set_client */;
>>>/*!40101 SET character_set_client = utf8 */;
>>>CREATE TABLE `TAGGABLE_LINK` (
>>> `LINK_ID` varchar(36) NOT NULL,
>>> `VERSION` int(11) NOT NULL,
>>> `ACTIVITY_REF` varchar(255) NOT NULL,
>>> `TAG_CRITERIA_REF` varchar(255) NOT NULL,
>>> `RUBRIC` text,
>>> `RATIONALE` text,
>>> `EXPORT_STRING` int(11) NOT NULL,
>>> `VISIBLE` bit(1) NOT NULL,
>>> `LOCKED` bit(1) NOT NULL,
>>> PRIMARY KEY (`LINK_ID`)
>>>) ENGINE=MyISAM DEFAULT CHARSET=utf8;
>>>/*!40101 SET character_set_client = @saved_cs_client */;
>>>
>>>--
>>>-- Dumping data for table `TAGGABLE_LINK`
>>>--
>>>
>>>LOCK TABLES `TAGGABLE_LINK` WRITE;
>>>/*!40000 ALTER TABLE `TAGGABLE_LINK` DISABLE KEYS */;
>>>/*!40000 ALTER TABLE `TAGGABLE_LINK` ENABLE KEYS */;
>>>UNLOCK TABLES;
>>>
>>>
>>>
>>>
>>>On Jul 12, 2011, at 10:40 AM, Maurer, Christopher Wayne wrote:
>>>
>>>David,
>>>I remember a bunch of strange issues with some past conversion scripts
>>>as
>>>well. I forget what the final outcome was, as stuff went in and out of
>>>the conversion scripts based on various errors from folks running the
>>>conversion. But those tables are related to OSP Matrix/Assignments (1
>>>and
>>>2) integration.
>>>
>>>Rows are created in the SITEASSOC_CONTEXT_ASSOCIATION table when you
>>>associate sites (currently done through a link in the Matrix tool).
>>>(as as aside, we will eventually investigate the duplication of
>>>functionality of this with the site linking that came in 2.7)
>>>
>>>To get records in TAGGABLE_LINK, you'd have to first make the above
>>>mentioned site association, then, you can link an assignment to a matrix
>>>cell (provided that you have created an assignment and a matrix!).
>>>
>>>Chris
>>>
>>>On 7/12/11 10:12 AM, "DAVID ROLDAN MARTINEZ"
>>><darolmar at upvnet.upv.es<mailto:darolmar at upvnet.upv.es>>
>>>wrote:
>>>
>>>
>>> Hi,
>>>
>>>Short description: Does anybody know what these tables are used for?
>>>
>>>Detailed description:
>>>
>>>We are on the process of migration from 2.6 to 2.8 and I've found two
>>>strange issues:
>>>* SITEASSOC_CONTEXT_ASSOCIATION is created at
>>>sakai_2_7_0_oracle_conversion.sql. I can create the table but it's
>>>empty.
>>>I've tried creating new objects (Assignments and Announcements) but it
>>>seems no to do nothing (no row is inserted in this table), though
>>>enabling hibernate.show_sql I've seen that Sakai tries to SELECT rows
>>>each that display assignment list. Does anybody know the aim of this
>>>table? where rows should be inserted?
>>>
>>>* TAGGLABLE_LINK. I haven't found this table at any of the migration
>>>scripts. However, when deleting as assignment tries to delete rows from
>>>it and, as it not exists, Oracle lauches an exception and the assignment
>>>can not be deleted. To top it off, Sakai locks the assignment and nobody
>>>can do anything with it. Searching in the code, I've found that is
>>>referenced in taggable module but, unfortunately, I don't know what's
>>>the
>>>intent of this module. To try to figure out when this table is created,
>>>I
>>>was thinking about to run migration scripts 2.6 -> 2.7 -> 2.8 and then
>>>set auto.ddl before to start Tomcat but I'm not sure if this will help.
>>>Any idea?
>>>
>>>I absolutely appreciate any suggestion, idea, etc. I'm really stuck with
>>>this. :(
>>>
>>>Thank you very much in advance.
>>>
>>>Cheers,
>>> David
>>>_______________________________________________
>>>sakai-dev mailing list
>>>sakai-dev at collab.sakaiproject.org<mailto:sakai-dev at collab.sakaiproject.o
>>>r
>>>g
>>>>
>>>http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>
>>>TO UNSUBSCRIBE: send email to
>>>sakai-dev-unsubscribe at collab.sakaiproject.org<mailto:sakai-dev-unsubscri
>>>b
>>>e
>>>@collab.sakaiproject.org> with a subject of
>>>"unsubscribe"
>>>
>>>_______________________________________________
>>>sakai-dev mailing list
>>>sakai-dev at collab.sakaiproject.org<mailto:sakai-dev at collab.sakaiproject.o
>>>r
>>>g
>>>>
>>>http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>
>>>TO UNSUBSCRIBE: send email to
>>>sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>>>"unsubscribe"
>>>
>>>
>>>
More information about the sakai-dev
mailing list