Hello Guys,
This may well be totally normal and expected behavior but to me it
seemed a little curious.
I have two objects:
Acknowledgment
Manufacturer
Manufacturer has a onetomany relationship with Acknowledgment in the
following manor:
<onetomany name="acknowledgement" lazy="true">
<link to="order.acknowledgement"
column="manufacturer_id" />
<collection type="array">
<order property="Created"
order="desc" />
</collection>
</onetomany>
Now what I've found is that if I set the parent manufacturer for the
acknowledgement like this:
<cfset
LOCAL.Acknowledgent.setParentManufacturer(LOCAL.Manufacturer) />
Despite the fact that I don't commit either of the objects, the cache
still effectively 'saves' the acknowledgment object, and upon reinit
of the application (at which point the cache is cleared) then the
acknowledgment record disappears.
Also, as a side note the method setParentManufacturer() seems to be
really very slow. Performance is terrible.
Is this the sort of behaviour you would expect from the cache? To my
mind an object should only be cached and a relationship saved if the
child is committed.
Thanks,
Robert
--
Before posting questions to the group please read:
http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer
Try out the new Transfer ORM Custom Google Search:
http://www.google.com/cse/home?cx=002375903941309441958:2s7wbd5ocb8
You received this message because you are subscribed to the Google Groups
"transfer-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/transfer-dev?hl=en
