Problem
The "Duplicate Row" option in the Browse Data tab almost always fails due to primary key or unique constraints. In practice, most SQLite tables have a PK, so the feature is unusable.

Expected behavior
Either:

• Allow duplication in a transaction buffer (like DBeaver), so the user can adjust PK/unique values before commit, or
• Hide/disable the "Duplicate Row" option when constraints make it impossible.

Actual behavior
DB Browser executes the duplicate immediately, causing a constraint violation. The option is prominently available but misleading.

Suggested resolution
Treat this as a usability bug:

• Remove or disable the "Duplicate Row" option when it cannot work, OR
• Rework transaction handling so duplication is possible before commit.

Notes
Other tools (e.g. DBeaver) allow duplication + editing before commit, so users expect similar behavior. As it stands, the option is confusing and feels broken.