BOR and Perfmance

[Michael Pokraka]

Hi Alon,
I think in theory if 'advance with dialog' works then it would also retai=
n
the object instance.
In practice however it just goes plain weird. I had an issue on 4.6c with=
 a
virtual attribute that didn't have a 'CLEAR' after the 'DATA' statement. =
Not
strictly necessary one may think...
WRONG! The attribute was used in the inbox description. Displaying it and
then clicking on another workitem which DIDN'T have a value for that
attribute would show the previous item's attribute value. So somehow it w=
as
buffered across instances when using the inbox.
I asked OSS about the theory/mechanics behind this without much success.
 
Could I also add to the original question the idea of a Persistent Object
Reference in this context... does that improve buffering or make it worse=
?
 
Cheers
Mike
 
Alon Raskin wrote:
> Hi Everyone,
>
> I trust that everyone had a good weekend.
>
> One of the nice things about the BOR is the buffering approach that it
> provides. When you first access a Dictionary attribute, the whole recor=
d is
> retrieved and stored in a structure so any subsequent accesses to Dicti=
onary
> attributes do not result in a call to the DB.
>
> My query is: Between two steps of a workflow, are all the BOR object
> instances re-instantiated? I got the feeling that they were but was uns=
ure.
> If that is the case then doesnt that defeat the whole purpose of the
> buffering approach?
>
> I look forward to your thoughts/comments.
>
> Alon
>
>