3

Mark modified tables dirty when transfering to another environement

In a multiple environment setup with for example DEV, TEST and PROD it would be optimal to have tables marked dirty when transfering to another environment to see all the changes compared to the original one.

Furthermore it opens up the possible to only deploy and execute dirty tables.

A comparison of the original project and the modified project should visualize the differences as dirty.

Br.

Michael

0 comments

Please sign in to leave a comment.