-
Bug
-
Resolution: Fixed
-
Low (View bug fix roadmap)
-
3.3.2
-
Orion 2.0.2, Oracle 91 w/ 10g thin driver
-
3.03
-
4
-
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
- is duplicated by
-
JRASERVER-14085 SearchRequest entity should use a extemely-long field types on Oracle 10g
- Closed
- is related to
-
JRASERVER-14544 The username in filtersubscription table is too short and does not match userbase
-
- Closed
-
-
JRASERVER-14701 OSPropertyText table should have the value column set to extremely-long datatype
- Closed
- relates to
-
JRASERVER-13329 Error when adding a group with name longer than 60 characters to a notification scheme: too long for database column
-
- Gathering Impact
-
This is a very disruptive change albeit a great fix. It involves customers re-creating databases and potentially running specific SQL scripts. So we have decided that 4.0 is the logical place for this change to happen.
And hence we have decided we dont wont to apply it to to their stable 3.13.x line.