RE: New proposal on Jira to drop support for derby and use docker instead

2022-03-08 Thread Development
From: Michael Brohl [michael.br...@ecomify.de] >Am 07.03.22 um 18:44 schrieb Development: >> So let me try to summarize your response: >> >> #1. The only reason to *keep* derby that you see is that we disagree on the >> relati

RE: New proposal on Jira to drop support for derby and use docker instead

2022-03-07 Thread Development
pull ofbiz/release18.12" (for a production/development version) * downloading ofbiz, going through the current instructions, trying to run it, {then often downloading the correct version of java and doing it again} Possible differences in our information could be: * Perhaps there are other diff

New proposal on Jira to drop support for derby and use docker instead

2022-03-06 Thread Development
I added a new proposal on Jira . It is a proposal to drop support for derby and use docker instead (You'll need to read the issue/proposal for that to make sense) The issue is at: https://issues.apache.org/jira/browse/OFBIZ-12588 This is a copy of the proposal: Derby is unique in the list of

Improper use of data model in EmplPositionType? - new JIRA issue created

2021-11-05 Thread Development
There is a new JIRA issue OFBIZ-12364 relating to how ofbiz is using the datamodel in Human Resources (in particular the EmplPositionType). If you are interested in the HR datamodels, come add your comments. CONFIDENTIALITY NOTICE: This message is intended only for the use of the person or

Uom seed data - new JIRA issues created

2020-10-02 Thread Development
There is a new JIRA issue OFBIZ-12036 relating to extending the seed units of measure, the unit of measure types, and the unit of measure conversions. A preliminary diff has been put up. Open to comments on it. A related OFBIZ-12037 JIRA issue was created relating to a bug found in the curre

Need input on extending the Uom Related seed data

2020-09-30 Thread Development
Hey everyone. I would like to contribute to trunk some more Uom (Uom, UomType, UomConversion) seed data, and some more demo records that use Uom data. I have found 2 issues that I will need input on before I can make a real proposal. ISSUE #1: There is a uomTypeId="TIME_FREQ_M

JIRA issue 12021 created for: RE: varchar(255) in fieldtypepostgres.xml

2020-09-22 Thread Development
[jacques.le.r...@les7arts.com] Sent: Tuesday, September 22, 2020 4:09 AM To: Development Cc: dev@ofbiz.apache.org Subject: Re: varchar(255) in fieldtypepostgres.xml Hi, Since this is more an OFBiz development (improvement) than its usage, I recommend to create a Jira issue https://issues.apache.o

RE: Welcome Aditya Sharma as new PMC member

2020-09-03 Thread Development
I was unaware of "brainstorming sessions" what platform are they on and when are they? From: Rishi Solanki [rishisolan...@gmail.com] Sent: Monday, August 24, 2020 6:22 AM To: dev@ofbiz.apache.org Subject: Re: Welcome Aditya Sharma as new PMC member Thank y

RE: varchar(255) in fieldtypepostgres.xml

2020-09-03 Thread Development
697590 This is also related https://markmail.org/message/xuwhnbmum3evejwk Jacques Le 10/08/2020 à 20:30, Development a écrit : > In /framework/entity/fieldtype/fieldtypepostgres.xml I saw some lines like: > > java-type="String"/> > java-type="String"

varchar(255) in fieldtypepostgres.xml

2020-08-10 Thread Development
In /framework/entity/fieldtype/fieldtypepostgres.xml I saw some lines like: In postgres, using "VARCHAR(255)" saves no space in the database over using "VARCHAR" (with no number) or "TEXT", the only difference is that the 255 slows it down with error checking. Is there any rea