Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-14085

SearchRequest entity should use a extemely-long field types on Oracle 10g

XMLWordPrintable

    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Currently the SearchRequest entity is defined like this :

       <entity entity-name="SearchRequest" table-name="searchrequest" package-name="">
             ...
              <field name="request" col-name="reqcontent" type="very-long"/>
      
          </entity>
      

      On Oracle 10g this is defined as varchar(4000). This means that search requests cant be bigger than that.

      It could be this :

       <entity entity-name="SearchRequest" table-name="searchrequest" package-name="">
             ...
              <field name="request" col-name="reqcontent" type="extremely-long"/>
      
          </entity>
      

      We had a customer who migrated from MYSQL (very-long ~ 32K) to ORACLE 10G and had problems because they had search requests > 4K

      We should up the limit for Oracle 10g in the next release of JIRA.

      We may want to consider other enities that use 'very-long' when we do this.

            Unassigned Unassigned
            bbaker ɹǝʞɐq pɐɹq
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: