[jira] [Updated] (OFBIZ-10150) supplierProductId Should Have Consistent Types Across Entities.
[ https://issues.apache.org/jira/browse/OFBIZ-10150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jesse thomas updated OFBIZ-10150: - Description: During some data migration I hit an issue where my data for supplierProductId was too long. So I looked up the fields and noticed that the order item entity had a different type for the field than the supplier product entity. I think it would be a good idea to pick one so the two fields can be treated consistently. I would vote for id-long, but I think either way it would be good to have them be the same type. There are other fields that have this issue too if you are interested? Thanks! applications/datamodel/entitydef/order-entitymodel.xml: applications/datamodel/entitydef/product-entitymodel.xml: was: During some data migration I hit an issue where my data for supplierProductId was too long. So I looked up the fields and noticed that the order entity had a different type for the field than the supplier product entity. I think it would be a good idea to pick one so the two fields can be treated consistently. I would vote for id-long, but I think either way it would be good to have them be the same type. There are other fields that have this issue too if you are interested? Thanks! applications/datamodel/entitydef/order-entitymodel.xml: applications/datamodel/entitydef/product-entitymodel.xml: > supplierProductId Should Have Consistent Types Across Entities. > --- > > Key: OFBIZ-10150 > URL: https://issues.apache.org/jira/browse/OFBIZ-10150 > Project: OFBiz > Issue Type: Bug > Components: order, product >Affects Versions: Trunk, Release Branch 16.11 > Environment: all >Reporter: jesse thomas >Priority: Minor > Fix For: Trunk, Release Branch 16.11 > > > During some data migration I hit an issue where my data for supplierProductId > was too long. So I looked up the fields and noticed that the order item > entity had a different type for the field than the supplier product entity. I > think it would be a good idea to pick one so the two fields can be treated > consistently. I would vote for id-long, but I think either way it would be > good to have them be the same type. There are other fields that have this > issue too if you are interested? > > Thanks! > applications/datamodel/entitydef/order-entitymodel.xml: > > applications/datamodel/entitydef/product-entitymodel.xml: > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9160) upgrade gradle to version 3.2.1
[ https://issues.apache.org/jira/browse/OFBIZ-9160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16316986#comment-16316986 ] Jacques Le Roux commented on OFBIZ-9160: I was not clear with this comment. For instance what to use if you put in a new feature? Obviously we miss something like "Upcoming Branch". I remembered Jacopo wrote ["Guidelines for resolving Jira tickets"|http://markmail.org/message/v3yswhnusu4elta5] on dev ML months ago but it seems something got wrong. The 17.12.01 version in Jira was created the 27/11/2017 (I guess by Jacopo), but then we postponed the creation of the 17.12.01 release branch in svn. I don't know if the previous "Upcoming Branch" has been renamed into 17.12.01 version in Jira but I just changed its date creation to 28/12/2017 and created a new "Upcoming Branch" antedated as if it was created the 28/12/2017. So we can now follow the schema Jacopo suggested :) > upgrade gradle to version 3.2.1 > --- > > Key: OFBIZ-9160 > URL: https://issues.apache.org/jira/browse/OFBIZ-9160 > Project: OFBiz > Issue Type: Improvement >Affects Versions: 17.12.01 >Reporter: Taher Alkhateeb >Priority: Minor > Labels: gradle, upgrade > Fix For: 17.12.01 > > > Upgrading the gradle build system to version 3.2.1 requires also upgrading > the buildbot scripts accordingly. > The proposal thread is referenced > [here|https://lists.apache.org/thread.html/4ba79bbd595f0d31f46b7402134b8392ecc5715098e93b2e5771b83f@%3Cdev.ofbiz.apache.org%3E] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-10150) supplierProductId Should Have Consistent Types Across Entities.
jesse thomas created OFBIZ-10150: Summary: supplierProductId Should Have Consistent Types Across Entities. Key: OFBIZ-10150 URL: https://issues.apache.org/jira/browse/OFBIZ-10150 Project: OFBiz Issue Type: Bug Components: order, product Affects Versions: Release Branch 16.11, Trunk Environment: all Reporter: jesse thomas Priority: Minor Fix For: Release Branch 16.11, Trunk During some data migration I hit an issue where my data for supplierProductId was too long. So I looked up the fields and noticed that the order entity had a different type for the field than the supplier product entity. I think it would be a good idea to pick one so the two fields can be treated consistently. I would vote for id-long, but I think either way it would be good to have them be the same type. There are other fields that have this issue too if you are interested? Thanks! applications/datamodel/entitydef/order-entitymodel.xml: applications/datamodel/entitydef/product-entitymodel.xml: -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-8230) Disentangle platform specific entity engine schemas
[ https://issues.apache.org/jira/browse/OFBIZ-8230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16315971#comment-16315971 ] Jacopo Cappellato commented on OFBIZ-8230: -- Some years ago I have suggested to the community something similar to what Pierre proposed in this ticket: at that time the general feedback has been that keeping the various configuration was useful and so I withdrew my proposal. If we want to review that decision I am fine either way but if the general feedback will not change I am in favor of closing this ticket as Michael has mentioned. > Disentangle platform specific entity engine schemas > --- > > Key: OFBIZ-8230 > URL: https://issues.apache.org/jira/browse/OFBIZ-8230 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Michael Brohl >Priority: Minor > Labels: database, devops, refactoring > Attachments: OFBIZ-8230-entityengine-postgresql.xml.patch, > OFBIZ-8230-entityengine.xml.patch > > > Disentangle entity engine schemas for specific rdbms platforms from > entityengine.xml -- This message was sent by Atlassian JIRA (v6.4.14#64029)
