Re: Fwd: Re: Re-2: oxid V6 MySQL transactions

2017-11-28 Thread K1 G.
nhaeu...@oxid-esales.com> Date: Mon, Nov 27, 2017 at 6:06 PM +0100 Subject: Re: Re-2: oxid V6 MySQL transactions To: "dev-general@lists.oxidforge.org" <dev-general@lists.oxidforge.org> Folks, could we please stick to English in this channel? Cheers! Marco Ursprü

Re: Fwd: Re: Re-2: oxid V6 MySQL transactions

2017-11-28 Thread Robert Blank
;mailto:marco.steinhaeu...@oxid-esales.com>> Date: Mon, Nov 27, 2017 at 6:06 PM +0100 Subject: Re: Re-2: oxid V6 MySQL transactions To: "dev-general@lists.oxidforge.org <mailto:dev-general@lists.oxidforge.org>" <dev-general@lists.oxidforge.org <mailto:dev

Re: Fwd: Re: Re-2: oxid V6 MySQL transactions

2017-11-27 Thread Keywan Ghadami
<marco.steinhaeu...@oxid-esales.com> Date: Mon, Nov 27, 2017 at 6:06 PM +0100 Subject: Re: Re-2: oxid V6 MySQL transactions To: "dev-general@lists.oxidforge.org" <dev-general@lists.oxidforge.org> Folks, could we please stick to English in this channel? Cheers! Mar

Re: Re-2: oxid V6 MySQL transactions

2017-11-27 Thread Marco Steinhaeuser
Folks, could we please stick to English in this channel? Cheers! Marco Ursprüngliche Nachricht Von: Robert Blank <robert.bl...@oxid-esales.com> Datum: 27.11.17 17:54 (GMT+01:00) An: dev-general@lists.oxidforge.org Betreff: Re: Re-2: oxid V6 MySQL transactions Hallo

Re: Re-2: oxid V6 MySQL transactions

2017-11-27 Thread Robert Blank
auf so ein Ereignis korrekt reagieren zu können, ohne dass man die eigenen log/transaktions-Daten in Dateien abspeichern muss! Mit freundlichen Grüßen Thomas Dartsch thomas.dart...@shopmodule.com  Original Message processed by david® ** *Re: oxid V6 MySQL transactions* (27

Re-2: oxid V6 MySQL transactions

2017-11-27 Thread oxid mailinglist
avid® Re: oxid V6 MySQL transactions (27-Nov-2017 16:00) From: Robert Blank To:dev-general@lists.oxidforge.org Hi, in your use-case this may sound strange, but this is by design. First by OXID eShop design: We want really _all_ database transactions to be rolled back, if a problem during

Re: oxid V6 MySQL transactions

2017-11-27 Thread Robert Blank
Hi, in your use-case this may sound strange, but this is by design. First by OXID eShop design: We want really _all_ database transactions to be rolled back, if a problem during e.g. the payment execution occurs. Then there is the design of the underlying DBAL: As we us Doctrine DBAL, we

oxid V6 MySQL transactions

2017-11-20 Thread oxid mailinglist
Hello guys, with oxid Version 6.0 the shop is using MySQL transactions. -> https://dev.mysql.com/doc/refman/5.7/en/commit.html For example this is used in OxidEsales\Eshop\Application\Model\Order::recalculateOrder (formally known as oxorder::recalculateOrder).