I didn't mean that modeling the inverse is something that should
"never" be done, but more that the Best Practice is to think about
the relationship, before you simply put it in the model.
One of the great things about using an EOGenerator-type tool is that
you can setup the relationship in
Am 05.12.2007 um 14:44 schrieb Mike Schrag:
It turns out to be almost never the case that you want to fetch all
"Open Tasks". It tends to be the case for us that you almost always
want to have additional qualifiers on those searches, which ends up
that you fault a HUGE (many thousands) of
Also it's an urban legend that simply faulting the objects is slow.
This is only true when you either have batch operations where you
are not really interested in the relationship but it will get
fetched because validation needs it. Or you have *huge*
relationships (say >1k objects).
For
Which may or may not be a good idea because you will fetch *every*
time you touch the relationship and this might suck a lot when used in
bindings (which you don't find via "Open Call Hierarchy") or you have
to cache it yourself but then have a bitch of a time to invalidate it
when you actu
Le 07-12-04 à 18:22, David LeBer a écrit :
On 4-Dec-07, at 6:09 PM, Owen McKerrow wrote:
Hi All,
As part of preparing to move to Eclipse we are going back and
updating our projects so they are using packages ( this is the bit
where I run and hide in shame as I have to admit we never used
I think this is a key "best practice". It is something that I
struggled with for a while, while trying to figure out why my
application was so slow. It's logical to add both relationships, but
once you understand what is happening, it is logical to leave the
heavy relationship off and use a
Be aware that if you have a two-way relationship where one side is
light, and one side is heavy, i.e.:
user <--->> transactions
You might want to call transaction.setUser(u) over
transaction.setUserRelationship(u), because the relationship call
has to fetch all the transactions for a g
On Dec 4, 2007, at 4:33 PM, Owen McKerrow wrote:
Hi Chuck, Miguel and Art,
Yup I see what your saying. I think the light just switched on, in
fact it did Art's email confirmed it.
As all the way through out the old projects we never had a method
called setPersonRelationship, just setPers
public void setPerson(edu.uow.ris.framework.eo.Person aValue) {
if( aValue == null ) {
edu.uow.ris.framework.eo.Person object = person();
if( object != null )
removeObjectFromBothSidesOfRelationshipWithKey( object, "person" );
} else
Hi Chuck, Miguel and Art,
Yup I see what your saying. I think the light just switched on, in
fact it did Art's email confirmed it.
As all the way through out the old projects we never had a method
called setPersonRelationship, just setPerson we dropped the word
Relationship from the templ
On Dec 4, 2007, at 3:09 PM, Owen McKerrow wrote:
public void setPerson(edu.uow.ris.framework.eo.Person aValue) {
if( aValue == null ) {
edu.uow.ris.framework.eo.Person object = person();
if( object != null )
removeObjectFromBothSidesOfRelationshipWit
On 4-Dec-07, at 6:09 PM, Owen McKerrow wrote:
Hi All,
As part of preparing to move to Eclipse we are going back and
updating our projects so they are using packages ( this is the bit
where I run and hide in shame as I have to admit we never used them
before ) and EOGenerator if they weren
Hi!
Well, you are calling addObjectToBothSidesOfRelationshipWithKey
( aValue, "person" ) inside the setPerson method. Assuming the
addObjectToBothSidesOfRelationshipWithKey will set the person using
key/value accessors, addObjectToBothSidesOfRelationshipWithKey will
call setPerson that w
On Dec 4, 2007, at 3:09 PM, Owen McKerrow wrote:
Hi All,
As part of preparing to move to Eclipse we are going back and
updating our projects so they are using packages ( this is the bit
where I run and hide in shame as I have to admit we never used them
before ) and EOGenerator if they w
Hi All,
As part of preparing to move to Eclipse we are going back and
updating our projects so they are using packages ( this is the bit
where I run and hide in shame as I have to admit we never used them
before ) and EOGenerator if they weren't already. Anyways.
We're having some is
15 matches
Mail list logo
