Idea : workaround the differences between Views/stored Func/Procs from different environments which only differ based on their Database prefix

When comparing different environments (live revisions), stored functions, procedures and views (from Snowflake, at least) are retrieved with their full definition (DB.SCHEMA.VIEW), contrary to the physical tables (only retrieved with SCHEMA.NAME), which generates perfectly understandable differences in the comparison feature, but yet this can hide actual differences between other objects. 

Idea : possibility to avoid retrieving or taking into account the DB name (which is totally inherent the a live environment definition, anyway - so when checking an environment, one already knows which DB it is connected to)