Floyd Marinescu wrote:
>
> On Mon, 21 Feb 2000 18:12:18 +0000, Mike Williams <[EMAIL PROTECTED]> wrote:
>
> >However, we've been bitten by the fact that an EB update does not always
> >result in an immediate database update (ie. the container may choose to
> >delay the ejbStore() until later). Thus, subsequent direct-SQL queries
> >within the same transaction might not see the changes!
> If you are trying to read sql from the database *within the same
> transaction as that where you did an update through your EJB* then
> it makes sense that the updated data would not be in the database.
> It won't be in the database because the transaction has not yet completed,
> thus the database has not yet committed the changes.
Almost correct.
It won't be in the database because the transaction has not yet
completed, thus the EJB server has not yet committed the changes. (EJB
users write-at-commit)
Changes made to the database are visible immediately in the same
transaction.
arkin
>
> Floyd
>
> ===========================================================================
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
> of the message "signoff EJB-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
--
----------------------------------------------------------------------
Assaf Arkin www.exoffice.com
CTO, Exoffice Technologies, Inc. www.exolab.org
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
