|
CqProvider caching old CqRecord data
|
 |
This question is not answered.
|
|
Replies:
1
-
Pages:
1
-
Last Post:
Sep 17, 2009 9:10 AM
Last Post By: bashboush
|
Threads:
[
Previous
|
Next
]
|
|
Posts:
19
Registered:
Jun 28, 2007 10:46:07 AM
|
|
|
|
CqProvider caching old CqRecord data
Posted:
Nov 12, 2007 01:45:11 AM
|
|
|
|
It appears that if a CqRecord object is read with Team API using doReadProperties, and if that record is then modified using cqWeb or another means, fetching that record again with the same CqProvider object that was used earlier, does not reflect the changes that were made between the two Team API calls. If I use a new CqProvider object, it does get the updates correctly, but with an added cost, as the first call with a new CqProvider object is significantly slower than subsequent calls.
So, Team API appears to be caching the old data, perhaps in the CqProvider object. I tried calling cqProvider.doClearContext() between calls, but that did not help. Is there a way to get Team API to check the repository so as to always get the latest data, without having to create a new CqProvider instance each time?
|
|
Posts:
3
Registered:
May 09, 2008 05:45:44 AM
|
|
|
|
Re: CqProvider caching old CqRecord data
Posted:
Sep 17, 2009 09:10:19 AM
in response to: navneet's post
|
|
|
|
Hi experts,
I am also having the same kind of problem.
I am wrting a migration programm, that duplicates a whole tre structure in Clearquest.
The program works fine until the first hook validation error occcurs.
From this point on the provider works with the sameCqRecord although I read with it other entities, and the programm can´t continue.
I also tried doClearContext(). But it didn´t help!
any idea?
|
|
|
|
|
