Hi Shweta,
Were you able to solve the problem?
Cheers
Paul Foxworthy
On 12 January 2017 at 17:02, Paul Foxworthy wrote:
> Hi Shweta,
>
> OK. Check the owners of the relevant inventory item or items. Are they
> Company too, or another party without accounting prefs?
>
> If that doesn't help, I
For example, a current project has some heavily used FinAccount rows and
the OFBiz implementation has a tendency to modify the child rows
(FinAccountAuth/FinAccountTrans) before modifying the parent FinAccount
row. This very easily results in a deadlock as soon as one of the
competing transactions
I'd suggest if possible, use MariaDB 5.5 or MySQL 5.7 and later instead. MySQL
5.6 is very bad performance, I tried to migrate our postgresql to MySQL 5.5/5.6
one month ago. Some of our sql scripts take less than 0.1s in postgresql and
MariaDB, but consume more than 100s in MySQL 5.5/5.6 :).
--
It is AWS Aurora variant of MySQL v5.6.10.
$ mysql -hofbiz.example.com -e 'select version(), @@aurora_version'
++--+
| version() | @@aurora_version |
++--+
| 5.6.10-log | 1.10 |
++--+
On Wed, Feb 15, 2
Hi Robb,
Just to be sure, the MySQL version you use >= 5.6.4 ?
Jacques
Le 15/02/2017 à 20:03, Robb Wagoner a écrit :
We are running OfBiz 12.04 and are using MySQL 5.6 as the RDBMS. We are
experiencing database deadlocks and would like to be able to add
MySQL-specific statements to deal with
Thanks Scott. Since I am new to OfBiz can you provide a code example? I.e.
by what means are you issuing an arbitrary no-op update statement on a
parent row?
On Wed, Feb 15, 2017 at 1:02 PM Scott Gray
wrote:
Hi Robb,
I've encountered similar deadlocks in the past and have simply issued an
updat
Hi Robb,
I've encountered similar deadlocks in the past and have simply issued an
update statement on the main row before attempting to work with any child
rows. That has the same effect as the FOR UPDATE statement but without
needing to enhance the framework.
Regards
Scott
On 16/02/2017 08:03,
We are running OfBiz 12.04 and are using MySQL 5.6 as the RDBMS. We are
experiencing database deadlocks and would like to be able to add
MySQL-specific statements to deal with the deadlocks. For example: `SELECT
... FOR UPDATE` on PRIMARY KEYs and/or FOREIGN KEYs in the transactions.
Being new to
Well .. manual is just going to the accounting app and adding transactions
by hand. So perhaps your starting point is the below screen
https://ofbiz-vm2.apache.org:8443/accounting/control/FindAcctgTrans?organizationPartyId=Company
On Feb 15, 2017 3:46 PM, "Moatasim Al Masri" wrote:
> Thank you
Thank you Taher
How can do it manual?
Best Regards,
Moatasim L. Al-Masri
Program Manager
P.O.Box 3516 Amman, 11821
The Hashemite Kingdom of Jordan
Tel. +962 (6) 556 2620
Mob (Jordan). +962 79 5426384
/biict
@biict
Kingdom of Saudi Arabia
Mob (KSA). +966 55 7
Hi Moatasim,
I'm assuming you mean you don't want to do manual data entry. If this is
the case then perhaps one way to do it is to create a data entity xml file
with all the transactions that you want and then load it from the webtools
or through the command line
On Feb 15, 2017 3:29 PM, "Moatasi
Dears
This is Moatasim, I need to upload opening balances for company, is there any
way to do that without heavy transactions entry?
Best Regards,
Moatasim L. Al-Masri
Program Manager
[Description: Logo for Office-4]
[Description: bi email-3-02]
P.O.Box 3516 Amman, 11821
The Hashemite Ki
Hi all,
I am looking forward to collaborate on this.
Best regards,
Pierre
On Tuesday, February 14, 2017, Dank Me wrote:
> Hey guys,
>
> Yeah sorry for the confusion. I asked on the dev group, Paul on the user
> group. :-)
>
> We are on the same team here. I believe Paul was wanting to see if
13 matches
Mail list logo