Hi Moritz,
I now found out, that Cx::C::ExtJS::REST invokes DBIC update itself, so
I've to move the transaction calls there.
I hope thats ok for you.
Greets,
Mario Minati
-------- Original-Nachricht --------
Betreff: Re: [html-formfu] RFC - Transactions for DBIC updates
Datum: Wed, 02 Sep 2009 22:10:31 +0200
Von: Mario Minati <mario.min...@googlemail.com>
An: HTML Form Creation, Rendering and Validation Framework
<html-formfu@lists.scsys.co.uk>
Referenzen: <4a9e60ba.2040...@googlemail.com>
<42736ba0-a63a-461a-8da6-6fffa64cb...@houseofdesign.de>
Hi Moritz,
I need transactions for my catalystx::controller::extjs::rest derived
classes, so I have no control over the line that calls update.
And I thought it would be me more usefull to put the code into
model::dbic than into extjs::rest.
Greets,
Mario
Moritz Onken schrieb:
Hi Mario,
as far as I remember nested transactions result in a noop. Which means
you can nest transactions and nothing bad will happen.
Other than that: what's wrong with $schema->txn_do {
$form->model->update } ?
cheers,
moritz
Am 02.09.2009 um 14:10 schrieb Mario Minati:
Hi @all,
I need to use transactions for all my db update and create actions.
Currently FF:M:DBIC doesn't support this. I'd like to extend the
update method to start a transaction, if an attribute is defined
(e.g. 'use_transaction').
To avoid nested transactions, as update is also called internally, I
would introduce a class variable which stores our transaction state.
Do you agree with that?
Greets,
Mario
_______________________________________________
HTML-FormFu mailing list
HTML-FormFu@lists.scsys.co.uk
http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/html-formfu
_______________________________________________
HTML-FormFu mailing list
HTML-FormFu@lists.scsys.co.uk
http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/html-formfu
