Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

This issue can't be edited

Because it belongs to an archived project. Jira admins can restore projects from the archive.

Consider adding an option to avoid DuplicateInsertPreventionStrategy.LOOK_UP extra lookup

Description

Some dialects natively detect an insertion of an already existing entry.

For the others we do an extra get to make sure the data is not present. We should offer the option to avoid that check entirely and let the user take the responsibility of only inserting things that are new.

Environment

None

Activity

Show:

Emmanuel BernardAugust 31, 2016 at 4:07 PM

yes but it cannot be set by the user, only the dialect implementor.

Gunnar MorlingAugust 31, 2016 at 2:15 PM

The idea behind NATIVE is to not do any additional checks. Instead a dialect would just raise a TupleAlreadyExistsException when issuing a write causing a duplicate-key-exception of sorts. So that's pretty much what you describe.

Details

Assignee

Reporter

Participants

Emmanuel Bernard
Gunnar Morling

Priority

Created August 31, 2016 at 2:10 PM
Updated August 31, 2016 at 4:07 PM