[ 
https://issues.apache.org/jira/browse/OFBIZ-8343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15711194#comment-15711194
 ] 

Pierre Smits commented on OFBIZ-8343:
-------------------------------------

Since your question is twofold,, Jacques, I will answer in kind.

1) No, I will not start a futile discussion on a specific issue that impacts 
the implementation of existing adopters. As both Michael and you expressed 
elsewhere in this issue, there seem to be functions in place to minimise that 
impact. Furthermore, you and your peers have expressed repeatedly - through 
words in the various OFBiz ML and through commits - not to care about the 
impact of OFBiz changes on adopters.
This issue now shows to 2 persons not apprehensive to include the patch in the 
code base, yet both desire a discussion in the dev ml. If they want (that) 
discussion so much, I suggest they start it (scratch their own itch) in stead 
of harassing others to do so.

2) No, we should not close this issue. This is a valid improvement. If you are 
so eager to have the list of issues minimised just for the sake of a minimal 
list, I suggest you start with revisiting the oldest ones on the list of open 
issues first and close those before you start working on more current issues.

> Make data type field length of id fields accept guid ids
> --------------------------------------------------------
>
>                 Key: OFBIZ-8343
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-8343
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: framework
>    Affects Versions: Trunk
>            Reporter: Pierre Smits
>            Assignee: Pierre Smits
>         Attachments: OFBIZ-8343-fieldtype-36.patch, OFBIZ-8343-fieldtype.patch
>
>
> Currently the length of id fields is limited to 20 characters. In order for 
> these fields to accept GUIIDs the length should be increased to 32 characters.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to