12103
100%
master: 88%

Ran 15 May 2018 04:08PM UTC

Jobs 1

Files 349

Run time 30s

Badge

Embed ▾

pending completion

Build # 12103

Build Type

push

travis-ci

Committed by

kyukhin

Commit Message

sql: allow ON CONFLICT REPLACE only for PK index

Constraints which require VDBE bytecode will be executed before making
insertion into Tarantool. For three major constraints - UNIQUE,
FOREIGN-KEY, CHECK the execution order doesn't matter if error action is
not REPLACE, because one constraint violation doesn't affect others.

But violation of constraint with ON CONFLICT REPLACE leads to a
removal of the whole tuple. When only PRIMARY KEY has REPLACE as
error action, it is not a problem and such behavior is absolutely
similar to Tarantool. But when we are dealing with secondary index
NOT NULL constraint with ON CONFLICT REPLACE, conflict in
secondary index leads to a whole tuple removal, and as a result
when there is also a conflict in primary key index, insertion
will lead to success instead of raising error.

In this patch possibility to create constraint non PRIMARY KEY
constraint with ON CONFLICT REPLACE has been banned, that kind of
behavior leads to a proper error message.

Closes #2963

Coverage Stats

60889 of 75420 relevant lines covered (80.73%)

1471254.26 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
3	12103.3 (TARGET=coverage)	15 May 2018 04:08PM UTC	0	80.73	Travis Job 12103.3

Source Files on build 12103

Detailed source file information is not available for this build.

tarantool / tarantool / 12103
100%
master: 88%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 12103

tarantool / tarantool / 12103 100% master: 88%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 12103

tarantool / tarantool / 12103
100%
master: 88%

README BADGES
x