Uploaded image for project: 'James Server'
  1. James Server
  2. JAMES-396

Wrong column order (IMHO) in primary key definition for SpoolRepositories.

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.2.0
    • Fix Version/s: 2.3.0
    • Component/s: None
    • Labels:
      None

      Description

      In sqlResources.xml many JDBCSpoolRepository createTable definition declare a primary key as (message_name, repository_name) instead of (repository_name, message_name) .
      this is "bad" for hypersonic, mysql, mssql, oracle, postgresql, sapdb
      db2 seems to be correctly configured.

      Why?

      AFAIK every query we do against the spool will include a filter on the repository_name. Some of them also includes the message_name but others does not include the message_name!

        Activity

        Hide
        bago Stefano Bagnara added a comment -

        This should perform better when a spool is really large (previously not using the key on the mail selection query)

        Show
        bago Stefano Bagnara added a comment - This should perform better when a spool is really large (previously not using the key on the mail selection query)
        Hide
        danny@apache.org Danny Angus added a comment -

        Closing issue fixed in released version.

        Show
        danny@apache.org Danny Angus added a comment - Closing issue fixed in released version.

          People

          • Assignee:
            bago Stefano Bagnara
            Reporter:
            bago Stefano Bagnara
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development