Hello, I just had the TOAD 2026 R1 installed. When I’m choosing “Duplicate Row” on a line in the grid, and then trying to change the PK in the new line, I’m getting “ORA-00001: unique constraint violated”. This happens before I even commit my changes, and while my Oracle –> Transactions –> Auto Commit option is disabled. My only way to get out of this is to rollback. I never had this problem in older versions of TOAD. Any idea how I can solve this? Thanks.
Hello,
I just tried this and could not reproduce any problem. Toad does not perform any commit with auto-commit disabled. But even if it did, rollback would not undo that.
If you click off of the newly inserted row before making changes that would prevent constraint violations, Toad will attempt the insert. Maybe that is what's happening. Or maybe you have a trigger on your table that is performing some work which is causing the problem.
-John
Hi There,
Thank you for your quick reply. I figured it out. It was a silly thing. In my older TOAD versions opting to duplicate the row would leave my cursor on the original line, then I would just move to the new line and manually change the PK. In this version, once hitting Duplicate Row the cursor automatically moves to the new line, and all I need to do is change the PK where the cursor is. But because I didn’t realize that I tried to move back to the original line (which I thought is the new line) thus triggering the error message. All is good. Sory for the bother.
1 Like