Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
M
mariadb
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
mariadb
Commits
e231e496
Commit
e231e496
authored
May 28, 2007
by
unknown
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Bug #28719: multi pk update ignore corrupts data
- 5.1 adoption
parent
c9d6ad13
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
3 additions
and
43 deletions
+3
-43
mysql-test/t/ndb_basic.test
mysql-test/t/ndb_basic.test
+3
-43
No files found.
mysql-test/t/ndb_basic.test
View file @
e231e496
...
...
@@ -767,7 +767,7 @@ drop table t1,t2;
# insert ignore
create
table
t1
(
a
int
not
null
primary
key
,
b
int
not
null
)
engine
=
ndb
;
insert
into
t1
values
(
1
,
10
),
(
2
,
20
),
(
3
,
30
);
--
error
ER_DUP_ENTRY
--
error
ER_DUP_ENTRY
_WITH_KEY_NAME
insert
into
t1
set
a
=
1
,
b
=
100
;
insert
ignore
into
t1
set
a
=
1
,
b
=
100
;
select
*
from
t1
order
by
a
;
...
...
@@ -780,12 +780,12 @@ create table t1 (a int not null primary key, b int not null) engine=ndb;
create
table
t2
(
c
int
not
null
primary
key
,
d
int
not
null
)
engine
=
ndb
;
insert
into
t1
values
(
1
,
10
),
(
2
,
10
),
(
3
,
30
),
(
4
,
30
);
insert
into
t2
values
(
1
,
10
),
(
2
,
10
),
(
3
,
30
),
(
4
,
30
);
--
error
ER_DUP_ENTRY
--
error
ER_DUP_ENTRY
_WITH_KEY_NAME
update
t1
set
a
=
1
where
a
=
3
;
select
*
from
t1
order
by
a
;
update
t1
set
b
=
1
where
a
>
1
order
by
a
desc
limit
1
;
select
*
from
t1
order
by
a
;
--
error
ER_DUP_ENTRY
--
error
ER_DUP_ENTRY
_WITH_KEY_NAME
update
t1
,
t2
set
a
=
1
,
c
=
1
where
a
=
3
and
c
=
3
;
select
*
from
t1
order
by
a
;
update
ignore
t1
,
t2
set
a
=
1
,
c
=
1
where
a
=
3
and
c
=
3
;
...
...
@@ -832,44 +832,4 @@ create table t2 like t1;
rename
table
t1
to
t10
,
t2
to
t20
;
drop
table
t10
,
t20
;
# delete
create
table
t1
(
a
int
not
null
primary
key
,
b
int
not
null
)
engine
=
ndb
;
create
table
t2
(
a
int
not
null
primary
key
,
b
int
not
null
)
engine
=
ndb
;
insert
into
t1
values
(
1
,
10
),
(
2
,
20
),
(
3
,
30
);
insert
into
t2
values
(
1
,
10
),
(
2
,
20
),
(
3
,
30
);
select
*
from
t1
order
by
a
;
delete
from
t1
where
a
>
0
order
by
a
desc
limit
1
;
select
*
from
t1
order
by
a
;
delete
from
t1
,
t2
using
t1
,
t2
where
t1
.
a
=
t2
.
a
;
select
*
from
t2
order
by
a
;
drop
table
t1
,
t2
;
# insert ignore
create
table
t1
(
a
int
not
null
primary
key
,
b
int
not
null
)
engine
=
ndb
;
insert
into
t1
values
(
1
,
10
),
(
2
,
20
),
(
3
,
30
);
--
error
ER_DUP_ENTRY_WITH_KEY_NAME
insert
into
t1
set
a
=
1
,
b
=
100
;
insert
ignore
into
t1
set
a
=
1
,
b
=
100
;
select
*
from
t1
order
by
a
;
insert
into
t1
set
a
=
1
,
b
=
1000
on
duplicate
key
update
b
=
b
+
1
;
select
*
from
t1
order
by
a
;
drop
table
t1
;
# update
create
table
t1
(
a
int
not
null
primary
key
,
b
int
not
null
)
engine
=
ndb
;
create
table
t2
(
c
int
not
null
primary
key
,
d
int
not
null
)
engine
=
ndb
;
insert
into
t1
values
(
1
,
10
),
(
2
,
10
),
(
3
,
30
),
(
4
,
30
);
insert
into
t2
values
(
1
,
10
),
(
2
,
10
),
(
3
,
30
),
(
4
,
30
);
--
error
ER_DUP_ENTRY_WITH_KEY_NAME
update
t1
set
a
=
1
where
a
=
3
;
select
*
from
t1
order
by
a
;
update
t1
set
b
=
1
where
a
>
1
order
by
a
desc
limit
1
;
select
*
from
t1
order
by
a
;
--
error
ER_DUP_ENTRY_WITH_KEY_NAME
update
t1
,
t2
set
a
=
1
,
c
=
1
where
a
=
3
and
c
=
3
;
select
*
from
t1
order
by
a
;
update
ignore
t1
,
t2
set
a
=
1
,
c
=
1
where
a
=
3
and
c
=
3
;
select
*
from
t1
order
by
a
;
drop
table
t1
,
t2
;
--
echo
End
of
5.1
tests
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment