Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-36172

Sequence name changed without database modification

    Details

    • 10 status:
      Resolved
    • Previous Issue Keys:
      SAM-2408

      Description

      This error is launched after migration to Sakai 10:

      org.sakaiproject.tool.assessment.services.assessment.PublishedAssessmentService - org.springframework.dao.InvalidDataAccessResourceUsageException: could not get next sequence value; SQL [select SAM_PUBATTACHMENT_ID_S.nextval from dual];

      This is due to the change at revision 305964.

      https://source.sakaiproject.org/websvn/comp.php?repname=sakai-svn&compare[0]=%2Fsam%2Ftrunk%2Fsamigo-hibernate%2Fsrc%2Fjava%2Forg%2Fsakaiproject%2Ftool%2Fassessment%2Fdata%2Fdao%2Fassessment%2FPublishedItemData.hbm.xml&compare[1]=%2Fsam%2Ftrunk%2Fsamigo-hibernate%2Fsrc%2Fjava%2Forg%2Fsakaiproject%2Ftool%2Fassessment%2Fdata%2Fdao%2Fassessment%2FPublishedItemData.hbm.xml&compare_rev[0]=305964&compare_rev[1]=305963

      That changes the name of the sequence from SAM_PUBLISHEDATTACHMENT_ID_S to SAM_PUBATTACHMENT_ID_S.

      I think this is a mistake due to merge or something like that but totally unintentional. If this change is on purpose then some code is needed in migration script to change sequence name.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  jaques@psybergate.co.za Jaques Smith (Inactive)
                  Reporter:
                  jjmerono@um.es Juan José Meroño Sánchez
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  10 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Git Source Code