-
15. Re: Re: Caching Virtual Stored Procedure Results
LDAP_USERView_WS has an XML parameter. That will cause caching to not be used.
-
16. Re: Caching Virtual Stored Procedure Results
Hi Steven,
So what would be your suggestion, If we are exposing the VBDs as web services wouldn't all our response be XML, so as per what you mentioned we will not be able to cache the WS invoke response at all. Is my understanding correct.
Also under what scenario would i be able to cache the response of all. Would writing a WS wrapper on a cache Virtual Procedure would do the trick ???
Any suggestions would help...
Also is there any approach for caching responses of VDB exposed as WS, that you are aware of ???
Thank you
RM
-
17. Re: Caching Virtual Stored Procedure Results
> Is my understanding correct
XML as a result is cachable. XML as an input parameter is not allowed as XML can be arbitrarily sized and is considered a non-comparable type. So if you have a procedure that is at a higher level with only non-lob input parameters, then you can introduce caching.
-
18. Re: Caching Virtual Stored Procedure Results
Hi Team,
Not sure if i understand you properly. So what you are saying is that since i am using WS to invoke my Virtual Procedure the input is XML that i am parsing inside the procedure. Due to that the the Procedure will not Cache the response against the input (XML) that i provided. So you suggestion is to have a child procedure call the data source models instead of the current design.
Is there a way to call Virtual SP from another Virtual SP. ??
Thank you
RPM
-
19. Re: Re: Caching Virtual Stored Procedure Results
Yes, having the user_profile_inputmsg as xml will cause the LDAP_USERView_USER_PROFILE.authNUSER to not be cachable:
CREATE VIRTUAL PROCEDURE "LDAP_USERView_USER_PROFILE.authNUSER"(IN USER_PROFILE_InputMsg xml OPTIONS (UUID 'mmuuid:0025f691-7265-45eb-b2a3-3572bac8c01b')) RETURNS TABLE ("Message Samples" xml ...
/*+ cache */
> Is there a way to call Virtual SP from another Virtual SP. ??
A virtual procedure call looks no different than calling a source procedure. So if you created a procedure that took uid and userPassword as string parameters it would be cachable.
-
20. Re: Caching Virtual Stored Procedure Results
Ranjith,
What SteveH is saying is since XML input to the procedure can NOT be cached the whole result of that procedure is not also cached. He suggesting, if you have a another procedure which took scalar values as input then that can be cached. So, have your procedure with XML input parse the values out and call this another stored procedure with scalar values, and cache the results of that child procedure.Yes, you can call one procedure from another "EXECUTE SP();"
Ramesh..