There's been some work on the transactions since the BETA-PROD-1
build. The BETA-PROD-2 build should be forthcoming shortly. Please try
again with that (when available) or the CVS version, and let us know
whether you still see the same problem. Though I didn't really follow
your example, since you didn't say what the transaction setting for 'A'
was, and I'm not sure how you worked with AutoCommit.
Aaron
On Mon, 2 Oct 2000, Davide Mora wrote:
> Hi,
>
> I'm trying to optimize my beans, but i have a strange
> behaviour using transactions: my bean 'B' have a
> method 'test' with the transaction type set to
> 'Required' while the 'B' transaction type is set to
> 'Supports'.
> 'Test' create 100 beans of type 'A' and exit.
> I checked the log, and when i call 'Test' the
> transaction is created and kept during the creation of
> the 'B' instances (the tx name still be the same), but
> it's about the 2x slower than using 'Supports' in both
> beans.
> The same test using JDBC, same database, same driver,
> same data take 1/5 if i use a transaction instead of
> autocommit.
>
> Another strange thing is that at the end of 'Test'
> appear many rows like that:
> [A] beforeCompletion called
> ...
> ...
> ...
> [A] afterCompletion called
> ...
> ...
> ...
>
> While i expect one one of each type, since i expect to
> have only one transaction.
>
> I'm using the BETA-PROD-01 downloaded from the web
> site, under windows 2000 with postgreSQL.
>
> /Davide
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Photos - 35mm Quality Prints, Now Get 15 Free!
> http://photos.yahoo.com/
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
