You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@turbine.apache.org by Jonas Denvall <jo...@arkatay.com> on 2002/08/28 19:00:44 UTC
caching of user-associated objects
Hi all.
I'm having some strange chaching problems with my generated objects. I
extended the TurbineUser with MyUser, and introduced a new table MyTable
with foreign key (userId) to MyUser.
The code
MyUser user = (MyUser) data.getUser();
MyTable myTable = user.getMyTable();
//update myTable
myTable.save();
works fine, the database is updated.
But in the next screen, I do myTable = data.getUser().getMyTable() again
- and that object is not updated! Why is that? Where is the caching
here? Am I doing the save() wrong? I don't understand what I'm doing
wrong - I'm making the changes on the object that is contained in the
User object in RunData.
Thanx,
Jonas
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>