"write db operator"

lghansselghansse Member Posts: 18 Contributor II
edited May 2019 in Help

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? 


Best Answer


  • Options
    lghansselghansse Member Posts: 18 Contributor II
    @Edin_Klapic, thank you! Should have thought about that myself  :#
  • Options
    M_MartinM_Martin RapidMiner Certified Analyst, Member Posts: 125 Unicorn
    I can confirm Edin's comment above - I ran into the same problem, and using Set Role was the answer.  If you ultimately want a column in your destination table to have a column to ensure row uniqueness, you could use the Execute SQL operator to append data just loaded with your Write Database operator to another table in your database that also includes an Identity type column that would populate (i.e. auto-number) as data is appended.  Best wishes, Michael Martin
Sign In or Register to comment.