-
Type:
Regression Bug
-
Status: Closed
-
Resolution: Fixed
-
Affects Version/s: 7.0.0 M5
-
Fix Version/s: 6.2.4 CE GA5, 6.2.X EE, 7.0.0 Alpha 1
-
Component/s: Portal Services, Portal Services > Expando
-
Labels:
-
Branch Version/s:6.2.x
-
Backported to Branch:Committed
-
Story Points:12
-
Fix Priority:3
-
Git Pull Request:
Data size support for default value of custom fields is different than their real values
Steps to reproduce it in Oracle 11.2 DB.
1. Start the server with an empty Oracle DB.
2. Check the data type for the respective columns in DB by running
SELECT TNAME, CNAME, COLTYPE FROM SYS.COL WHERE TNAME IN ('EXPANDOVALUE', 'EXPANDOCOLUMN') AND CNAME IN ('DATA_' , 'DEFAULTDATA');
Result
TNAME | CNAME | COLTYPE |
---|---|---|
EXPANDOCOLUMN | DEFAULTDATA | VARCHAR2 |
EXPANDOVALUE | DATA_ | CLOB |
Expected: Both columns are CLOB.
- depends on
-
LPS-55889 Custom Fields doesn't save in Oracle with more than 4000 chars
- Closed
- is caused by
-
LPS-45937 Web Form portlet fails to submit when field "comment" is over 2000 characters on SQLServer - java.sql.BatchUpdateException: Data truncation occurs in the log due to the limitation in ExpandoValue "data_": nvarchar(2000)
- Closed
- relates
-
LPE-14261 Default values of custom fields should support the same size that are supported by the values
-
- Closed
-