add a field called 'content' to the custRequest entity
------------------------------------------------------ Key: OFBIZ-1904 URL: https://issues.apache.org/jira/browse/OFBIZ-1904 Project: OFBiz Issue Type: Improvement Components: order Affects Versions: SVN trunk Reporter: Hans Bakker Priority: Minor Fix For: SVN trunk We get in customer requests with a reasonable size text, most of the time longer than 255 characters. Currently there is no field with that size in the custRequest entity. The propasal is to add a field called 'content' and the type 'CLOB' to this entity. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
[ https://issues.apache.org/jira/browse/OFBIZ-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12618576#action_12618576 ] Hans Bakker commented on OFBIZ-1904: ------------------------------------ need a mimetype too, so in total: <field name="contentMimeTypeId" type="id-long"/> <field name="content" type="very-long"></field> > add a field called 'content' to the custRequest entity > ------------------------------------------------------ > > Key: OFBIZ-1904 > URL: https://issues.apache.org/jira/browse/OFBIZ-1904 > Project: OFBiz > Issue Type: Improvement > Components: order > Affects Versions: SVN trunk > Reporter: Hans Bakker > Priority: Minor > Fix For: SVN trunk > > > We get in customer requests with a reasonable size text, most of the time longer than 255 characters. Currently there is no field with that size in the custRequest entity. > The propasal is to add a field called 'content' and the type 'CLOB' to this entity. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12618577#action_12618577 ] David E. Jones commented on OFBIZ-1904: --------------------------------------- Details are meant to go in the CustRequestItem entity, not in the CustRequest entity itself. In fact, you really shouldn't have a CustRequest record without at least one CustRequestItem. > add a field called 'content' to the custRequest entity > ------------------------------------------------------ > > Key: OFBIZ-1904 > URL: https://issues.apache.org/jira/browse/OFBIZ-1904 > Project: OFBiz > Issue Type: Improvement > Components: order > Affects Versions: SVN trunk > Reporter: Hans Bakker > Priority: Minor > Fix For: SVN trunk > > > We get in customer requests with a reasonable size text, most of the time longer than 255 characters. Currently there is no field with that size in the custRequest entity. > The propasal is to add a field called 'content' and the type 'CLOB' to this entity. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hans Bakker closed OFBIZ-1904. ------------------------------ Resolution: Invalid there is a CLOB on the Item level, indicated by David, which can be used. > add a field called 'content' to the custRequest entity > ------------------------------------------------------ > > Key: OFBIZ-1904 > URL: https://issues.apache.org/jira/browse/OFBIZ-1904 > Project: OFBiz > Issue Type: Improvement > Components: order > Affects Versions: SVN trunk > Reporter: Hans Bakker > Priority: Minor > Fix For: SVN trunk > > > We get in customer requests with a reasonable size text, most of the time longer than 255 characters. Currently there is no field with that size in the custRequest entity. > The propasal is to add a field called 'content' and the type 'CLOB' to this entity. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
Free forum by Nabble | Edit this page |