Comments
1 comment
-
You will have to select either of the fields to be unique in order to guarantee that the generated data will satisfy the unique constraint. Without setting either of the columns to unique the generated data may not satisfy the constraint because the tool may generate data that is not unique for the combination of the two fields.
Add comment
Please sign in to leave a comment.
I am trying to create test data, by creating a schema based on the database schema of the TPC-C benchmark. I also added some indexes, but now I encountered a weird warning from SQL Data Generator:
This unique constraint is a composite primary key, consisting of two fields: As far as I understand it, this means that the combination of the two fields is unique. So, why would I need to select unique for either of the two fields? Am I missing something, or is this a bug?