Roenbaeck/anchor

Feature request: fix idempotency problem on Vertica projections

Closed this issue · 1 comments

When generating SQL code with following settings (as shown on screenshot), the app creates SQL code with "CREATE PROJECTION" statement (shown on second screenshot).
When run generated script second time (i.e., after adding new objects), it fails with "projection XXX already exists" error, so the script is slightly unidempotent. However, Vertica allows to run "CREATE PROJECTION IF NOT EXISTS" statement, which fixes the problem.

image
image

Sorry for the delay, this is now fixed in: 86d51ca
It is available in the test version of the online modeler.