Closed stagha closed 1 year ago
Hello, As you can see there's a PR in the works for solving this issue with Generated columns and Generated Identity columns. Hopefully this will merge soon and you won't see this issue anymore.
As a side note, if you'd like to try out our premium database subsetter that has loads more features and does not face this issue, feel free to sign up for a free trial here
This issue should be fixed now!
A standard pattern is for an identity column to be defined like this:
However, condenser does not appear to be able to handle such columns gracefully. It should be possible to force insert a value in such a column using
OVERRIDING SYSTEM VALUE
as described here. This is indicated in the error message as well.This issue touches on GENERATED columns, but is not quite the same as it just asks for the ability to exclude such columns from the sub-setting operation. Identity columns are non-null and are key to the foreign key relationships that the tool would preserve, so excluding them would not solve the problem.