~drizzle-trunk/drizzle/development

« back to all changes in this revision

Viewing changes to tests/t/status.test

  • Committer: Monty Taylor
  • Date: 2010-03-11 18:27:20 UTC
  • mfrom: (1333 staging)
  • mto: This revision was merged to the branch mainline in revision 1348.
  • Revision ID: mordred@inaugust.com-20100311182720-hd1h87y6cb1b1mp0
Merged trunk.

Show diffs side-by-side

added added

removed removed

Lines of Context:
15
15
 
16
16
 
17
17
select 1;
 
18
--replace_column 2 #
18
19
show status like 'last_query_cost';
19
20
create temporary table t1 (a int) engine=myisam;
20
21
insert into t1 values (1),(2),(3),(4),(5),(6),(7),(8),(9),(10);
23
24
insert into t1 values (1),(2),(3),(4),(5),(6),(7),(8),(9),(10);
24
25
insert into t1 values (1),(2),(3),(4),(5),(6),(7),(8),(9),(10);
25
26
select * from t1 where a=6;
 
27
--replace_column 2 #
26
28
show status like 'last_query_cost';
27
29
# Ensure value dosn't change by second status call
 
30
--replace_column 2 #
28
31
show status like 'last_query_cost';
29
32
select 1;
 
33
--replace_column 2 #
30
34
show status like 'last_query_cost';
31
35
drop table t1;
32
36
 
72
76
 
73
77
# Prerequisite.
74
78
SHOW STATUS LIKE 'max_used_connections';
75
 
SELECT * FROM INFORMATION_SCHEMA.SESSION_STATUS WHERE VARIABLE_NAME LIKE 'max_used_connections';
 
79
SELECT * FROM data_dictionary.SESSION_STATUS WHERE VARIABLE_NAME LIKE 'max_used_connections';
76
80
 
77
81
# Save original setting.
78
82
connect (con1,localhost,root,,);
85
89
 
86
90
# Check that max_used_connections still reflects maximum value.
87
91
SHOW STATUS LIKE 'max_used_connections';
88
 
SELECT * FROM INFORMATION_SCHEMA.SESSION_STATUS WHERE VARIABLE_NAME LIKE 'max_used_connections';
 
92
SELECT * FROM data_dictionary.SESSION_STATUS WHERE VARIABLE_NAME LIKE 'max_used_connections';
89
93
 
90
94
#
91
95
# Bug #30377: EXPLAIN loses last_query_cost when used with UNION