2012-04-22 01:00:30.103676+00:00
https://api.launchpad.net/1.0/bugs/986731
https://api.launchpad.net/1.0/~elenst
https://api.launchpad.net/1.0/maria/+milestone/5.1
https://api.launchpad.net/1.0/bugs/986731/linked_branches
https://api.launchpad.net/1.0/bugs/986731/activity
https://bugs.launchpad.net/bugs/986731
Elena Stepanova
Sergey Petrunia
Maria 5.1
sql-bench/test-table-elimination fails with SQL syntax error in LOCK TABLES if executed with --lock-tables
New
Low
2012-04-22 00:15:07.395896+00:00
do_query($dbh,"LOCK TABLES elim_facts WRITE, elim_attr1 WRITE, elim_attr2 WRITE");
207c207
< do_query($dbh,"LOCK TABLES elim_facts, elim_attr1, elim_attr2 WRITE");
---
> do_query($dbh,"LOCK TABLES elim_facts WRITE, elim_attr1 WRITE, elim_attr2 WRITE");
but then another one reveals:
testing full facts facts table
Error occured with execute(select * from elim_current_facts where id=30246.3207346651)
-> Table 'F' was not locked with LOCK TABLES
This happens because the view elim_current_facts addresses the table elim_facts through its alias F, which is not locked explicitly. So, I also added the view itself into the LOCK statement:
95c95
< do_query($dbh,"LOCK TABLES elim_facts, elim_attr1, elim_attr2 WRITE");
---
> do_query($dbh,"LOCK TABLES elim_current_facts WRITE, elim_facts WRITE, elim_attr1 WRITE, elim_attr2 WRITE");
207c207
< do_query($dbh,"LOCK TABLES elim_facts, elim_attr1, elim_attr2 WRITE");
---
> do_query($dbh,"LOCK TABLES elim_current_facts WRITE, elim_facts WRITE, elim_attr1 WRITE, elim_attr2 WRITE");
Now it passes.
bzr version-info
revision-id:
date: 2012-04-06 13:31:33 +0500
build-date: 2012-04-22 04:12:58 +0400
revno: 3146
According to the script code, should also be reproducible on 5.2-5.5.
To reproduce,
- start MariaDB server;
- run perl test-table-elimination --socket= --lock-tables]]>
bug
Elena Stepanova
added bug
summary
Elena Stepanova
Elena Stepanova
do_query($dbh,"LOCK TABLES elim_facts WRITE, elim_attr1 WRITE, elim_attr2 WRITE");
207c207
< do_query($dbh,"LOCK TABLES elim_facts, elim_attr1, elim_attr2 WRITE");
---
> do_query($dbh,"LOCK TABLES elim_facts WRITE, elim_attr1 WRITE, elim_attr2 WRITE");
but then another one reveals:
testing full facts facts table
Error occured with execute(select * from elim_current_facts where id=30246.3207346651)
-> Table 'F' was not locked with LOCK TABLES
This happens because the view elim_current_facts addresses the table elim_facts through its alias F, which is not locked explicitly. So, I also added the view itself into the LOCK statement:
95c95
< do_query($dbh,"LOCK TABLES elim_facts, elim_attr1, elim_attr2 WRITE");
---
> do_query($dbh,"LOCK TABLES elim_current_facts WRITE, elim_facts WRITE, elim_attr1 WRITE, elim_attr2 WRITE");
207c207
< do_query($dbh,"LOCK TABLES elim_facts, elim_attr1, elim_attr2 WRITE");
---
> do_query($dbh,"LOCK TABLES elim_current_facts WRITE, elim_facts WRITE, elim_attr1 WRITE, elim_attr2 WRITE");
Now it passes.
bzr version-info
revision-id: holyfoot@askmonty.org-20120406083133-j6s0hqnkaimuct1r
date: 2012-04-06 13:31:33 +0500
build-date: 2012-04-22 04:12:58 +0400
revno: 3146
According to the script code, should also be reproducible on 5.2-5.5.
To reproduce,
- start MariaDB server;
- run perl test-table-elimination --socket= --lock-tables]]>