-
Suggestion
-
Resolution: Fixed
The property text table should use the extremely-long data type for its value column so that on databases such as Oracle, CLObs are used instead of limited VARCHAR columns.
- details
-
JRASERVER-17430 Planning for the initial investigation
-
- Closed
-
-
JRASERVER-17462 Document the JIRA v4.0 DB upgrade guide.
-
- Closed
-
- is related to
-
JRASERVER-17954 Different definitions for entity field type "very-long" for different DB systems causes DB incompatibilities, and therefore errors on import.
-
- Closed
-
-
JRASERVER-15880 OSPropertyString table should have the value column set to extremely-long datatype
- Closed
- relates to
-
JRASERVER-8293 Import fails if searchrequest:request data too large
-
- Closed
-
OSPropertyText table should have the value column set to extremely-long datatype
-
Suggestion
-
Resolution: Fixed
The property text table should use the extremely-long data type for its value column so that on databases such as Oracle, CLObs are used instead of limited VARCHAR columns.
- details
-
JRASERVER-17430 Planning for the initial investigation
-
- Closed
-
-
JRASERVER-17462 Document the JIRA v4.0 DB upgrade guide.
-
- Closed
-
- is related to
-
JRASERVER-17954 Different definitions for entity field type "very-long" for different DB systems causes DB incompatibilities, and therefore errors on import.
-
- Closed
-
-
JRASERVER-15880 OSPropertyString table should have the value column set to extremely-long datatype
- Closed
- relates to
-
JRASERVER-8293 Import fails if searchrequest:request data too large
-
- Closed
-