Michael,

> If yes, my question is, how all the RDBO internals work with such a setup. If 
> I remember correctly 
> RDBO wraps complex saves or deletes within a transaction. Would this lead to 
> something like 
> nested transactions? Is this possible at all, with sqlite (I am using now) 
> and postgres (I would like 
> to use after some more learning)?

The documentation consistently says:

  "Only if it is NOT already in a transaction".

Hence, if you pass the Rose::DB object that has a transaction placed on 
it manually (as per the tutorial) I don't think it would cause nested 
transactions.

The SQLITE website isn't clear whether sqlite can do nested transactions 
but a google search consistently turns up answers that say no.

> And if it works in principle do I have to stuff the $dbh manually into every 
> RDBO object or does it 
> "just work" because Apache::DBI takes care that RDBO gets the right (perhaps 
> reused) handle 
> even if RDBO always requests a fresh one?

One would assume that your assumption is correct however I've always 
discovered that the only way to _know_ is to:

1) Perform exhaustive and closed tests
    (i.e. test all possible combinations)

2) Take control of [the thing I'm testing] myself

3) Perform a risk analysis and determine if the risk is more than I'm
    prepared to accept

It seems you're trying to test a multi-user, multi-thread environment 
which can be tricky bests to do (1) with. Doing (3) could be dangerous 
to you and doing (2) seems like a reasonable, if conservative, bet to me :)

DSL

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Rose-db-object mailing list
Rose-db-object@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rose-db-object

Reply via email to