Hi Andrus,
I was experimenting with a TransactionFilter, which like the
DataContextFilter was trying to provide a carefree transaction around
web requests. I see that this is not going to work with transactions
as they are bound to resources. The use case was handling the
situation where the app
BTW, if there's no commit or rollback, and the transaction stays open
indefinitely, this would result in quick connection pool exhaustion.
So why would you do that?
Andrus
On Mar 9, 2008, at 7:19 PM, Andrus Adamchik wrote:
This could be a DB artifact. E.g. with MySQL MyISAM tables. Which DB
This could be a DB artifact. E.g. with MySQL MyISAM tables. Which DB
are you using?
Andrus
On Mar 8, 2008, at 5:53 AM, Malcolm Edgar wrote:
I have been playing around this in a web context, and what I am
finding with a user created Transaction, if the DataContext commits
the changes, unless
I have been playing around this in a web context, and what I am
finding with a user created Transaction, if the DataContext commits
the changes, unless the Transaction explicitly performs a rollback the
changes will be committed to the database.
This is not what I was expecting, but I am wondering
Great! Thanks for that.
regards Malcolm Edgar
On Feb 19, 2008 11:18 AM, Andrus Adamchik <[EMAIL PROTECTED]> wrote:
> Just use your own transactions, then 'commitChanges' turns into 'flush':
>
> http://cayenne.apache.org/doc/understanding-transactions.html
>
> Andrus
>
>
> On Feb 18, 2008, at 7:49
Just use your own transactions, then 'commitChanges' turns into 'flush':
http://cayenne.apache.org/doc/understanding-transactions.html
Andrus
On Feb 18, 2008, at 7:49 AM, Malcolm Edgar wrote:
Hi Ari,
thanks for the response. This would be a very good 3.0 feature if it
is not already present
Hi Ari,
thanks for the response. This would be a very good 3.0 feature if it
is not already present.
In Hibernate this functionality is performed as a flush operation,
where CRUD operations are performed against the transaction but are
not actually committed.
Would this would cause issues with
On 18/02/2008, at 2:07 PM, Malcolm Edgar wrote:
Is there a way in Cayenne, possibly using Transactions, that we can
perform this import, do inserts and queries against the transaction
and only commit/rollback at the end?
Subclass the Cayenne context, override performQuery and add in your
ow
Hi All,
We had an issue a while ago where we were performing an large XML
import into a database using Cayenne.
What we wanted to do was to insert data, as we parsed the XML, because
in latter code we wanted to perform SQL queries to determine the
existence of records. The import was not into an
