[jira] [Commented] (OFBIZ-8343) Make data type field length of id fields accept guid ids
[ https://issues.apache.org/jira/browse/OFBIZ-8343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15817017#comment-15817017 ] Scott Gray commented on OFBIZ-8343: --- It certainly didn't come across as friendly IMO, considering you of all people know that contributors are free to "scratch their itch" on any topic they chose to. To quote you from the past: bq. I wonder where the respect for the volunteer (spending his precious time, scratching his itch, improving the product) is > 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)
[jira] [Commented] (OFBIZ-8343) Make data type field length of id fields accept guid ids
[ https://issues.apache.org/jira/browse/OFBIZ-8343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15816999#comment-15816999 ] Pierre Smits commented on OFBIZ-8343: - Non taken, And I have provided you with feedback and a little friendly advice. > 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)
[jira] [Commented] (OFBIZ-8343) Make data type field length of id fields accept guid ids
[ https://issues.apache.org/jira/browse/OFBIZ-8343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15816195#comment-15816195 ] Scott Gray commented on OFBIZ-8343: --- bq. Furthermore, why don't you work your own issues to successful conclusion first, and then work your way through unassigned issues before you start considering closing issues worked on by others. My apologies if you've taken offense to my review and/or follow up. I was simply interested in the topic and the motivations behind using GUUIDs. I'll step back from the discussion and we can perhaps pick it up again when you'd like this to be considered for inclusion in the code base. > 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)
[jira] [Commented] (OFBIZ-8316) Update Apache Solr/Lucene to release 6.2.1
[ https://issues.apache.org/jira/browse/OFBIZ-8316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15816074#comment-15816074 ] Jacques Le Roux commented on OFBIZ-8316: Ah, since I did not assign to me the "Start Progress" button does not appear, please Jinghai do. > Update Apache Solr/Lucene to release 6.2.1 > -- > > Key: OFBIZ-8316 > URL: https://issues.apache.org/jira/browse/OFBIZ-8316 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/lucene, specialpurpose/solr >Affects Versions: Trunk >Reporter: Michael Brohl >Assignee: Shi Jinghai >Priority: Minor > Attachments: OFBIZ-8316_corrected.patch, > ofbiz-truck-lucene-6.2.1.patch, ofbiz-truck-solr-6.2.1.patch, > solr6.2.1_1.patch > > > According to the announcements in > https://lists.apache.org/thread.html/5d2cb1ecbe04c6c40b8eeba3b7f8da586d1271af98c9b07ceee8ada2@%3Cannounce.apache.org%3E > and > https://lists.apache.org/thread.html/c1269b52229f6bce68399e813b7c6b79eb3f6283ae21bde11c82fc7c@%3Cannounce.apache.org%3E > there is a new Solr/Lucene release available. > This issue takes care of the update. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-8316) Update Apache Solr/Lucene to release 6.2.1
[ https://issues.apache.org/jira/browse/OFBIZ-8316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-8316: -- Assignee: Shi Jinghai (was: Michael Brohl) > Update Apache Solr/Lucene to release 6.2.1 > -- > > Key: OFBIZ-8316 > URL: https://issues.apache.org/jira/browse/OFBIZ-8316 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/lucene, specialpurpose/solr >Affects Versions: Trunk >Reporter: Michael Brohl >Assignee: Shi Jinghai >Priority: Minor > Attachments: OFBIZ-8316_corrected.patch, > ofbiz-truck-lucene-6.2.1.patch, ofbiz-truck-solr-6.2.1.patch, > solr6.2.1_1.patch > > > According to the announcements in > https://lists.apache.org/thread.html/5d2cb1ecbe04c6c40b8eeba3b7f8da586d1271af98c9b07ceee8ada2@%3Cannounce.apache.org%3E > and > https://lists.apache.org/thread.html/c1269b52229f6bce68399e813b7c6b79eb3f6283ae21bde11c82fc7c@%3Cannounce.apache.org%3E > there is a new Solr/Lucene release available. > This issue takes care of the update. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-8316) Update Apache Solr/Lucene to release 6.2.1
[ https://issues.apache.org/jira/browse/OFBIZ-8316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15816070#comment-15816070 ] Jacques Le Roux commented on OFBIZ-8316: Actually the official commit process the OFBiz project uses is CTR (Commit Then Review) not RTC. Of course things should be taken with a grain of salt, and in this case # Jinghai should have assigned the issue to himself when he committed # Before that the "Provide Patch" button should have been pushed by the person who provided the patch (caopengan here) # Then the "Start Progress" button should have been pushed (by Jinghai since he started by committing in 1st place) I'm doing it for you now guys, please remember, thanks! > Update Apache Solr/Lucene to release 6.2.1 > -- > > Key: OFBIZ-8316 > URL: https://issues.apache.org/jira/browse/OFBIZ-8316 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/lucene, specialpurpose/solr >Affects Versions: Trunk >Reporter: Michael Brohl >Assignee: Michael Brohl >Priority: Minor > Attachments: OFBIZ-8316_corrected.patch, > ofbiz-truck-lucene-6.2.1.patch, ofbiz-truck-solr-6.2.1.patch, > solr6.2.1_1.patch > > > According to the announcements in > https://lists.apache.org/thread.html/5d2cb1ecbe04c6c40b8eeba3b7f8da586d1271af98c9b07ceee8ada2@%3Cannounce.apache.org%3E > and > https://lists.apache.org/thread.html/c1269b52229f6bce68399e813b7c6b79eb3f6283ae21bde11c82fc7c@%3Cannounce.apache.org%3E > there is a new Solr/Lucene release available. > This issue takes care of the update. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (OFBIZ-8316) Update Apache Solr/Lucene to release 6.2.1
[ https://issues.apache.org/jira/browse/OFBIZ-8316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shi Jinghai updated OFBIZ-8316: --- Comment: was deleted (was: Hi Jacques, Sorry, I'm totally wrong. Today Cao Pengan helped me to reproduce the error you found locally. It's the products index couldn't be recogonized by solr after running loadDefault. I don't know why, but the content index is OK (the content index can be generated by running test lucene component). Setting it as solrdefault in runtime/indexes/index.properties: index=content, start ofbiz, in this case solr works fine. We'll try to find how to resolve this problem. Kind Regards,) > Update Apache Solr/Lucene to release 6.2.1 > -- > > Key: OFBIZ-8316 > URL: https://issues.apache.org/jira/browse/OFBIZ-8316 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/lucene, specialpurpose/solr >Affects Versions: Trunk >Reporter: Michael Brohl >Assignee: Michael Brohl >Priority: Minor > Attachments: OFBIZ-8316_corrected.patch, > ofbiz-truck-lucene-6.2.1.patch, ofbiz-truck-solr-6.2.1.patch, > solr6.2.1_1.patch > > > According to the announcements in > https://lists.apache.org/thread.html/5d2cb1ecbe04c6c40b8eeba3b7f8da586d1271af98c9b07ceee8ada2@%3Cannounce.apache.org%3E > and > https://lists.apache.org/thread.html/c1269b52229f6bce68399e813b7c6b79eb3f6283ae21bde11c82fc7c@%3Cannounce.apache.org%3E > there is a new Solr/Lucene release available. > This issue takes care of the update. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-8316) Update Apache Solr/Lucene to release 6.2.1
[ https://issues.apache.org/jira/browse/OFBIZ-8316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15815323#comment-15815323 ] Shi Jinghai commented on OFBIZ-8316: Hi Jacques, Sorry, I'm totally wrong. Today Cao Pengan helped me to reproduce the error you found locally. It's the products index couldn't be recogonized by solr after running loadDefault. I don't know why, but the content index is OK (the content index can be generated by running test lucene component). Setting it as solrdefault in runtime/indexes/index.properties: index=content, start ofbiz, in this case solr works fine. We'll try to find how to resolve this problem. Kind Regards, > Update Apache Solr/Lucene to release 6.2.1 > -- > > Key: OFBIZ-8316 > URL: https://issues.apache.org/jira/browse/OFBIZ-8316 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/lucene, specialpurpose/solr >Affects Versions: Trunk >Reporter: Michael Brohl >Assignee: Michael Brohl >Priority: Minor > Attachments: OFBIZ-8316_corrected.patch, > ofbiz-truck-lucene-6.2.1.patch, ofbiz-truck-solr-6.2.1.patch, > solr6.2.1_1.patch > > > According to the announcements in > https://lists.apache.org/thread.html/5d2cb1ecbe04c6c40b8eeba3b7f8da586d1271af98c9b07ceee8ada2@%3Cannounce.apache.org%3E > and > https://lists.apache.org/thread.html/c1269b52229f6bce68399e813b7c6b79eb3f6283ae21bde11c82fc7c@%3Cannounce.apache.org%3E > there is a new Solr/Lucene release available. > This issue takes care of the update. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-8316) Update Apache Solr/Lucene to release 6.2.1
[ https://issues.apache.org/jira/browse/OFBIZ-8316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15815322#comment-15815322 ] Shi Jinghai commented on OFBIZ-8316: Hi Jacques, Sorry, I'm totally wrong. Today Cao Pengan helped me to reproduce the error you found locally. It's the products index couldn't be recogonized by solr after running loadDefault. I don't know why, but the content index is OK (the content index can be generated by running test lucene component). Setting it as solrdefault in runtime/indexes/index.properties: index=content, start ofbiz, in this case solr works fine. We'll try to find how to resolve this problem. Kind Regards, > Update Apache Solr/Lucene to release 6.2.1 > -- > > Key: OFBIZ-8316 > URL: https://issues.apache.org/jira/browse/OFBIZ-8316 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/lucene, specialpurpose/solr >Affects Versions: Trunk >Reporter: Michael Brohl >Assignee: Michael Brohl >Priority: Minor > Attachments: OFBIZ-8316_corrected.patch, > ofbiz-truck-lucene-6.2.1.patch, ofbiz-truck-solr-6.2.1.patch, > solr6.2.1_1.patch > > > According to the announcements in > https://lists.apache.org/thread.html/5d2cb1ecbe04c6c40b8eeba3b7f8da586d1271af98c9b07ceee8ada2@%3Cannounce.apache.org%3E > and > https://lists.apache.org/thread.html/c1269b52229f6bce68399e813b7c6b79eb3f6283ae21bde11c82fc7c@%3Cannounce.apache.org%3E > there is a new Solr/Lucene release available. > This issue takes care of the update. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-8316) Update Apache Solr/Lucene to release 6.2.1
[ https://issues.apache.org/jira/browse/OFBIZ-8316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15815185#comment-15815185 ] Michael Brohl commented on OFBIZ-8316: -- Please don't misunderstand me: it's not about making failures, it's about the process. But I won't insist on this any more... > Update Apache Solr/Lucene to release 6.2.1 > -- > > Key: OFBIZ-8316 > URL: https://issues.apache.org/jira/browse/OFBIZ-8316 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/lucene, specialpurpose/solr >Affects Versions: Trunk >Reporter: Michael Brohl >Assignee: Michael Brohl >Priority: Minor > Attachments: OFBIZ-8316_corrected.patch, > ofbiz-truck-lucene-6.2.1.patch, ofbiz-truck-solr-6.2.1.patch, > solr6.2.1_1.patch > > > According to the announcements in > https://lists.apache.org/thread.html/5d2cb1ecbe04c6c40b8eeba3b7f8da586d1271af98c9b07ceee8ada2@%3Cannounce.apache.org%3E > and > https://lists.apache.org/thread.html/c1269b52229f6bce68399e813b7c6b79eb3f6283ae21bde11c82fc7c@%3Cannounce.apache.org%3E > there is a new Solr/Lucene release available. > This issue takes care of the update. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-8316) Update Apache Solr/Lucene to release 6.2.1
[ https://issues.apache.org/jira/browse/OFBIZ-8316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15815181#comment-15815181 ] Michael Brohl commented on OFBIZ-8316: -- Default is /data in solr home. See https://cwiki.apache.org/confluence/display/solr/DataDir+and+DirectoryFactory+in+SolrConfig You can specify the solr home dynamically with -Dsolr.solr.home=/Users/foo/ofbiz/specialpurpose/solr/home (using the old way to start OFBiz through ofbiz.jar, I have not the time to look how it works with gradle at the moment). > Update Apache Solr/Lucene to release 6.2.1 > -- > > Key: OFBIZ-8316 > URL: https://issues.apache.org/jira/browse/OFBIZ-8316 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/lucene, specialpurpose/solr >Affects Versions: Trunk >Reporter: Michael Brohl >Assignee: Michael Brohl >Priority: Minor > Attachments: OFBIZ-8316_corrected.patch, > ofbiz-truck-lucene-6.2.1.patch, ofbiz-truck-solr-6.2.1.patch, > solr6.2.1_1.patch > > > According to the announcements in > https://lists.apache.org/thread.html/5d2cb1ecbe04c6c40b8eeba3b7f8da586d1271af98c9b07ceee8ada2@%3Cannounce.apache.org%3E > and > https://lists.apache.org/thread.html/c1269b52229f6bce68399e813b7c6b79eb3f6283ae21bde11c82fc7c@%3Cannounce.apache.org%3E > there is a new Solr/Lucene release available. > This issue takes care of the update. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-8316) Update Apache Solr/Lucene to release 6.2.1
[ https://issues.apache.org/jira/browse/OFBIZ-8316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15815143#comment-15815143 ] Jacques Le Roux commented on OFBIZ-8316: I confirm I do the same :) > Update Apache Solr/Lucene to release 6.2.1 > -- > > Key: OFBIZ-8316 > URL: https://issues.apache.org/jira/browse/OFBIZ-8316 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/lucene, specialpurpose/solr >Affects Versions: Trunk >Reporter: Michael Brohl >Assignee: Michael Brohl >Priority: Minor > Attachments: OFBIZ-8316_corrected.patch, > ofbiz-truck-lucene-6.2.1.patch, ofbiz-truck-solr-6.2.1.patch, > solr6.2.1_1.patch > > > According to the announcements in > https://lists.apache.org/thread.html/5d2cb1ecbe04c6c40b8eeba3b7f8da586d1271af98c9b07ceee8ada2@%3Cannounce.apache.org%3E > and > https://lists.apache.org/thread.html/c1269b52229f6bce68399e813b7c6b79eb3f6283ae21bde11c82fc7c@%3Cannounce.apache.org%3E > there is a new Solr/Lucene release available. > This issue takes care of the update. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-8316) Update Apache Solr/Lucene to release 6.2.1
[ https://issues.apache.org/jira/browse/OFBIZ-8316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15815142#comment-15815142 ] Jacques Le Roux commented on OFBIZ-8316: Thanks Jinghai, I wanted to look into this in detail to see if we can find a way to have something set for OFBiz OOTB. So I Googled for "solr set dataDir dynamically" but I'm short of time atm. Did you think at it already? > Update Apache Solr/Lucene to release 6.2.1 > -- > > Key: OFBIZ-8316 > URL: https://issues.apache.org/jira/browse/OFBIZ-8316 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/lucene, specialpurpose/solr >Affects Versions: Trunk >Reporter: Michael Brohl >Assignee: Michael Brohl >Priority: Minor > Attachments: OFBIZ-8316_corrected.patch, > ofbiz-truck-lucene-6.2.1.patch, ofbiz-truck-solr-6.2.1.patch, > solr6.2.1_1.patch > > > According to the announcements in > https://lists.apache.org/thread.html/5d2cb1ecbe04c6c40b8eeba3b7f8da586d1271af98c9b07ceee8ada2@%3Cannounce.apache.org%3E > and > https://lists.apache.org/thread.html/c1269b52229f6bce68399e813b7c6b79eb3f6283ae21bde11c82fc7c@%3Cannounce.apache.org%3E > there is a new Solr/Lucene release available. > This issue takes care of the update. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-9170) Department wise Trial balance in an internal organization
velusamy created OFBIZ-9170: --- Summary: Department wise Trial balance in an internal organization Key: OFBIZ-9170 URL: https://issues.apache.org/jira/browse/OFBIZ-9170 Project: OFBiz Issue Type: New Feature Components: ALL COMPONENTS Reporter: velusamy Dear Support team, Want to configure one internal organization and multiple Trail Balance based on the departments ( which will help to get dept wise Balance sheet and P ), is this possible to achieve in ofbiz with the default functionalities. Please help Regards, Velu Remov -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8316) Update Apache Solr/Lucene to release 6.2.1
[ https://issues.apache.org/jira/browse/OFBIZ-8316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] caopengan updated OFBIZ-8316: - Attachment: solr6.2.1_1.patch Because of updated solr6.2.1, solr5.2.1 used in project page file is useless, so this time will be useless HTML files deleted > Update Apache Solr/Lucene to release 6.2.1 > -- > > Key: OFBIZ-8316 > URL: https://issues.apache.org/jira/browse/OFBIZ-8316 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/lucene, specialpurpose/solr >Affects Versions: Trunk >Reporter: Michael Brohl >Assignee: Michael Brohl >Priority: Minor > Attachments: OFBIZ-8316_corrected.patch, > ofbiz-truck-lucene-6.2.1.patch, ofbiz-truck-solr-6.2.1.patch, > solr6.2.1_1.patch > > > According to the announcements in > https://lists.apache.org/thread.html/5d2cb1ecbe04c6c40b8eeba3b7f8da586d1271af98c9b07ceee8ada2@%3Cannounce.apache.org%3E > and > https://lists.apache.org/thread.html/c1269b52229f6bce68399e813b7c6b79eb3f6283ae21bde11c82fc7c@%3Cannounce.apache.org%3E > there is a new Solr/Lucene release available. > This issue takes care of the update. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-8316) Update Apache Solr/Lucene to release 6.2.1
[ https://issues.apache.org/jira/browse/OFBIZ-8316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] caopengan updated OFBIZ-8316: - Attachment: (was: patch.txt) > Update Apache Solr/Lucene to release 6.2.1 > -- > > Key: OFBIZ-8316 > URL: https://issues.apache.org/jira/browse/OFBIZ-8316 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/lucene, specialpurpose/solr >Affects Versions: Trunk >Reporter: Michael Brohl >Assignee: Michael Brohl >Priority: Minor > Attachments: OFBIZ-8316_corrected.patch, > ofbiz-truck-lucene-6.2.1.patch, ofbiz-truck-solr-6.2.1.patch > > > According to the announcements in > https://lists.apache.org/thread.html/5d2cb1ecbe04c6c40b8eeba3b7f8da586d1271af98c9b07ceee8ada2@%3Cannounce.apache.org%3E > and > https://lists.apache.org/thread.html/c1269b52229f6bce68399e813b7c6b79eb3f6283ae21bde11c82fc7c@%3Cannounce.apache.org%3E > there is a new Solr/Lucene release available. > This issue takes care of the update. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-8343) Make data type field length of id fields accept guid ids
[ https://issues.apache.org/jira/browse/OFBIZ-8343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15814565#comment-15814565 ] Pierre Smits commented on OFBIZ-8343: - There are numerous places throughout OFBiz where id fields can be set manually, just do a simple search on: * "" * Id* The mere fact of having this decreases the UX as duplication may occur when entering manually or importing existing data through the webtools/import functions, or when migrating from an existing RDBMS solution to a new (RDBMS/newSQL) solution. Also, using a uuid requires less complexities to ensure uniqueness when applied to clustered implementations (multiple OFBiz apps servers combined with HAFO RDBMS solutions, or even newSQL solutions) compared to having sequenced Ids. With sequenced Id the migration process to a new rdbms (or newSQL) solution of requires a lot more effort than when using uuids. There are also numerous entities where a sequenced Id is not required per se as the primary Id, e.g. * the various Type entities * the various Attribute entities * JobSandbox * Visit * Visitor * The various entities that require compounded primary key definitions to ensure uniqueness. Using a sequence num should only be used where it is required by external factors, such as business process or local law (which is mainly for human convenience purposes, e.g invoice numbering). It should have been the exception, is stead of the norm. Furthermore, why don't you work your own issues (https://issues.apache.org/jira/issues/?jql=project%20%3D%20OFBIZ%20AND%20resolution%20%3D%20Unresolved%20AND%20assignee%20%3D%20lektran%20ORDER%20BY%20priority%20DESC) to successful conclusion first, and then work your way through unassigned issues ()https://issues.apache.org/jira/issues/?jql=project%20%3D%20OFBIZ%20AND%20resolution%20%3D%20Unresolved%20AND%20assignee%20is%20EMPTY%20ORDER%20BY%20priority%20DESC) before you start considering closing issues worked on by others. > 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)
