Currently when deploying objects and selecting dependencies cache databases are treated differently than other data sources. With standard data sources only tables in the lineage of the selected objects are included in the car file. For caching, every table within the entire database is included. For areas with multiple tables and multiple developers, this can easily have nasty consequences where something that is not ready to be deployed gets caught up with something that is ready for testing.
Any update on when/if this will be done? Our prod environment just had another outage because a cache table that was under development was promoted when it should not have been...