|I have been working with databases for a long time,
|and particularly with Oracle, I am not aware that this
|can happen, whether in transaction or not, before
|commit, nobody can see the updated table period in the
|database..
well that is my point precisely, it seems to imply that the updates "before
the commit" are seen by connections enrolled in the SAME transaction THROUGH
THE DATABASE.... and frankly I am a bit skeptical as to the level of
support for these features in the db or even if they exist at all or are
just "wishful features" (heck they don't even support 2pc and xa right)...
so this smells of "teen spirit" to me... by requiring "inflight" visibility
of the changed records they put a difficult requirement on the db drivers
and I don't see it working well.
They could have just required lock steps, as in first commit the changes
(and the db can follow that semantic) and then issue your findBy as just
another query...
I am no db expert (they are rare these days) but it strikes me as a
misguided requirement.
Bill for example couldn't you get the same functionality with the
serialiazed commits? Is this functionality that you couldn't get otherwise?
you are the first one to require this feature (and you are savvy enough to
scratch your itch so that is cool but still I wonder...)
but the REAL question is "is it true that you cannot see changed tables from
a connection participating in the SAME transaction that changed it in the
first place?"
regards
marcf
|
|I don't know much about XA, it having its own set of
|rules though.
|
|__________________________________________________
|Do You Yahoo!?
|Spot the hottest trends in music, movies, and more.
|http://buzz.yahoo.com/
|
|_______________________________________________
|Jboss-development mailing list
|[EMAIL PROTECTED]
|http://lists.sourceforge.net/lists/listinfo/jboss-development
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
