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

Possible Regression on Oracle Conversion for SAKAI_CLUSTER

    XMLWordPrintable

Details

    • Task
    • Status: CLOSED
    • Blocker
    • Resolution: Fixed
    • 2.9.x
    • 2.9.x
    • Kernel
    • None

    Description

      In KNL-725, the field was converted to TIMESTAMP WITH TIME ZONE, however this was reported by two people to cause problems with clusters going out of Sync.

      This entire issue came up because both Omer (at rice)
      http://collab.sakaiproject.org/pipermail/sakai-dev/2012-September/018931.html
      And Jaco (At opencollab)
      http://collab.sakaiproject.org/pipermail/sakai-dev/2012-September/019064.html

      said that there were warnings about sessions getting closed and clusters leaving when the field on SAKAI_CLUSTER was converted by the 2.9.x script to "TIMESTAMP WITH TIME ZONE". It should fix the DST problem but caused this other problem.

      Leaving it as DATETIME (the existing field type) would still leave the DST problem, converting to TIMESTAMP would give you increased precision but still leave the DST problem.

      I believe that converting to TIMESTAMP WITH LOCAL TIME ZONE could potentially resolve both clustering and DST, or it might break still break the clustering. I'm going to commit this fix.

      There was also a commit to KNL-734 which changed SAKAI_EVENT and SAKAI_SESSION which should also match this type.

      Gliffy Diagrams

        Zeplin

          Attachments

            Issue Links

              Activity

                People

                  jonespm Matthew Jones
                  jonespm Matthew Jones
                  Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Git Integration