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

Import fails if searchrequest:request data too large

    XMLWordPrintable

Details

    Description

      Entity "SearchRequest" has field "request" of type "very-long"
      Needs to be "extremely-long" for import into Oracle as standalone instance seemed to allow longer content length than 4000 characters. (that whole clob thing)

      Throws:
      ORA-01461: can bind a LONG value only for insert into a LONG column

      Attachments

        Issue Links

          is duplicated by

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

          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-14544 The username in filtersubscription table is too short and does not match userbase

          • Low - Low priority issues
          • Gathering Impact

          Suggestion - JRASERVER-14701 OSPropertyText table should have the value column set to extremely-long datatype

          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-13329 Error when adding a group with name longer than 60 characters to a notification scheme: too long for database column

          • Medium - Medium priority issues
          • Gathering Impact

          Activity

            People

              mlassau Mark Lassau (Inactive)
              57b2883d76f9 Eric White
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: