The question is not so much whether you use a different DataContext
or not, but rather how do you get a hold of your object. I suspect
you fetch a table X and then read data for table Y via a
relationship... and this is Y that is giving you trouble... ? In this
case you may want to use prefetching on "xy" relationship whenever
you retrieve X. Side effect of prefetching is that is refreshes
objects related to the main objects of the query.
On Nov 23, 2005, at 3:15 PM, Jürgen Saar wrote:
> I have a problem with cayenne 1.1 :
> We have an old inhouse software and
> a web software based on cayenne and cocoon and tomcat
> all seems fine but there are some tables with texts
> that are fitted with 1:1 relation to other tables.
> When the old software changes one of these texts the
> web application, even after hours, shows the old text.
> For ervery request, I use a new created DataContext
> I thought that would prevent such behavior.
> What can I do, to prevent data caching?
> --- Juergen ---
This archive was generated by hypermail 2.0.0 : Wed Nov 23 2005 - 11:28:43 EST