Is there a way to force DD to refresh its cache of the dbschema without stopping and starting the server?
We ran into this problem today while trying to develop our DD client config. If you make changes, DD doesn't refresh its cache with regard to the dbschema and then complains about all sorts of things. Stop and start the server - run the exact same deployment, and DD is happy.
It seems to me that DD should maintain a timestamp on the files it caches and be able to determine if it needs to reload them when a run is started by comparing the current timestamp with the cached timestamp.
--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com