As soon as I read the headline of this entry, I thought "Jake found a clean way around the caching?! SWEET!".
You could always issue a 'dbcache flush' command from your WSQ agent? ;-)
In truth, this is why I tend to not use profiles in my web-based or hybrid apps but rather documents.
Hopefully someone out there's got a more solid solution than dropping cache just so a single databases profile changes can be seen from the web instantly!
As soon as I read the headline of this entry, I thought "Jake found a clean way around the caching?! SWEET!".
You could always issue a 'dbcache flush' command from your WSQ agent? ;-)
In truth, this is why I tend to not use profiles in my web-based or hybrid apps but rather documents.
Hopefully someone out there's got a more solid solution than dropping cache just so a single databases profile changes can be seen from the web instantly!
-Chris