"write db operator"
Hi,
I'm currently using the the write database operator (with overwrite mode: overwrite first, append then) as part of a process. When The database is being written I get an error 'Database error occurred: (conn:13694) Duplicate entry '128230' for key 'PRIMARY''. I checked the column specifics and indeed, one of the columns is added as a primary key (see also below). However, I've never defined this attribute as a key (and it shouldn't be). Does anybody know how to prevent the writing operator to see and write this as a key?
I'm currently using the the write database operator (with overwrite mode: overwrite first, append then) as part of a process. When The database is being written I get an error 'Database error occurred: (conn:13694) Duplicate entry '128230' for key 'PRIMARY''. I checked the column specifics and indeed, one of the columns is added as a primary key (see also below). However, I've never defined this attribute as a key (and it shouldn't be). Does anybody know how to prevent the writing operator to see and write this as a key?
Find more posts tagged with
Sort by:
1 - 3 of
31
Sort by:
1 - 1 of
11
The column contact_id in your ExampleSet probably has the RapidMiner Role id. This is seen as marker to set this column as key.
Solution:
Use Set Role to change the Role of this column either to something different. You can even create a Role of your choice.
But remember: Each Role can only occur once in an ExampleSet.
Happy Mining,
Edin