Dear Vinay,
> No. Not really. Its is just that the new Oracle release clearly state
> advantages of using rowids for updates and it is very attractive to have
> that kind of a facility for updates and deletes on huge tables [we do have
> quite a few tables that are in excess of 5-6 million records]. The idea is
> to have the option at hand so that it can be used as and when required
> [which is going to be quite a lot].
Agreed.
> Issues like the client accessing the bean immediately after creation
are
> things applications take care of by design - proper transactions and a
> decent session facade that ensures that screw ups don't happen.
would be better your code would check for a null or empty rowIDValue
and then fall back to using the PK field(s), so it would be safe
even after create! (Tried to find that in your source on the list,
couldn't find that check, but may me I'm too tired yet).
regards
Georg
___ ___
| + | |__ Georg Rehfeld Woltmanstr. 12 20097 Hamburg
|_|_\ |___ [EMAIL PROTECTED] +49 (40) 23 53 27 10
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
