2001-09-28 07:05:54 +02:00
|
|
|
drop table if exists t1,t2;
|
2005-09-22 02:23:07 +02:00
|
|
|
drop view if exists v1;
|
2001-09-28 07:05:54 +02:00
|
|
|
CREATE TABLE t1 (c int not null, d char (10) not null);
|
|
|
|
|
insert into t1 values(1,""),(2,"a"),(3,"b");
|
|
|
|
|
CREATE TEMPORARY TABLE t1 (a int not null, b char (10) not null);
|
|
|
|
|
insert into t1 values(4,"e"),(5,"f"),(6,"g");
|
|
|
|
|
alter table t1 rename t2;
|
|
|
|
|
select * from t1;
|
2000-12-28 02:56:38 +01:00
|
|
|
c d
|
|
|
|
|
1
|
|
|
|
|
2 a
|
|
|
|
|
3 b
|
2001-09-28 07:05:54 +02:00
|
|
|
select * from t2;
|
2000-12-28 02:56:38 +01:00
|
|
|
a b
|
|
|
|
|
4 e
|
|
|
|
|
5 f
|
|
|
|
|
6 g
|
2001-09-28 07:05:54 +02:00
|
|
|
CREATE TABLE t2 (x int not null, y int not null);
|
|
|
|
|
alter table t2 rename t1;
|
|
|
|
|
select * from t1;
|
2000-12-28 02:56:38 +01:00
|
|
|
a b
|
|
|
|
|
4 e
|
|
|
|
|
5 f
|
|
|
|
|
6 g
|
2003-12-10 05:31:42 +01:00
|
|
|
create TEMPORARY TABLE t2 engine=heap select * from t1;
|
|
|
|
|
create TEMPORARY TABLE IF NOT EXISTS t2 (a int) engine=heap;
|
2005-09-12 14:09:19 +02:00
|
|
|
Warnings:
|
|
|
|
|
Note 1050 Table 't2' already exists
|
2001-09-28 07:05:54 +02:00
|
|
|
CREATE TEMPORARY TABLE t1 (a int not null, b char (10) not null);
|
2003-06-04 17:28:51 +02:00
|
|
|
ERROR 42S01: Table 't1' already exists
|
2001-09-28 07:05:54 +02:00
|
|
|
ALTER TABLE t1 RENAME t2;
|
2003-06-04 17:28:51 +02:00
|
|
|
ERROR 42S01: Table 't2' already exists
|
2001-09-28 07:05:54 +02:00
|
|
|
select * from t2;
|
2000-12-28 02:56:38 +01:00
|
|
|
a b
|
|
|
|
|
4 e
|
|
|
|
|
5 f
|
|
|
|
|
6 g
|
2001-09-28 07:05:54 +02:00
|
|
|
alter table t2 add primary key (a,b);
|
|
|
|
|
drop table t1,t2;
|
|
|
|
|
select * from t1;
|
2000-12-28 02:56:38 +01:00
|
|
|
c d
|
|
|
|
|
1
|
|
|
|
|
2 a
|
|
|
|
|
3 b
|
2001-09-28 07:05:54 +02:00
|
|
|
drop table t2;
|
|
|
|
|
create temporary table t1 select *,2 as "e" from t1;
|
|
|
|
|
select * from t1;
|
2000-12-28 02:56:38 +01:00
|
|
|
c d e
|
|
|
|
|
1 2
|
|
|
|
|
2 a 2
|
|
|
|
|
3 b 2
|
2001-09-28 07:05:54 +02:00
|
|
|
drop table t1;
|
|
|
|
|
drop table t1;
|
|
|
|
|
CREATE TABLE t1 (pkCrash INTEGER PRIMARY KEY,strCrash VARCHAR(255));
|
|
|
|
|
INSERT INTO t1 ( pkCrash, strCrash ) VALUES ( 1, '1');
|
|
|
|
|
SELECT CONCAT_WS(pkCrash, strCrash) FROM t1;
|
2000-12-28 02:56:38 +01:00
|
|
|
CONCAT_WS(pkCrash, strCrash)
|
|
|
|
|
1
|
2001-09-28 07:05:54 +02:00
|
|
|
drop table t1;
|
|
|
|
|
create temporary table t1 select 1 as 'x';
|
|
|
|
|
drop table t1;
|
|
|
|
|
CREATE TABLE t1 (x INT);
|
|
|
|
|
INSERT INTO t1 VALUES (1), (2), (3);
|
|
|
|
|
CREATE TEMPORARY TABLE tmp SELECT *, NULL FROM t1;
|
|
|
|
|
drop table t1;
|
|
|
|
|
create temporary table t1 (id int(10) not null unique);
|
|
|
|
|
create temporary table t2 (id int(10) not null primary key,
|
|
|
|
|
val int(10) not null);
|
|
|
|
|
insert into t1 values (1),(2),(4);
|
|
|
|
|
insert into t2 values (1,1),(2,1),(3,1),(4,2);
|
|
|
|
|
select one.id, two.val, elt(two.val,'one','two') from t1 one, t2 two where two.id=one.id order by one.id;
|
2000-12-28 02:56:38 +01:00
|
|
|
id val elt(two.val,'one','two')
|
|
|
|
|
1 1 one
|
|
|
|
|
2 1 one
|
|
|
|
|
4 2 two
|
2001-09-28 07:05:54 +02:00
|
|
|
drop table t1,t2;
|
2002-12-05 15:38:49 +01:00
|
|
|
create temporary table t1 (a int not null);
|
|
|
|
|
insert into t1 values (1),(1);
|
|
|
|
|
alter table t1 add primary key (a);
|
2006-01-23 12:17:05 +01:00
|
|
|
ERROR 23000: Duplicate entry '1' for key 'PRIMARY'
|
2002-12-05 15:38:49 +01:00
|
|
|
drop table t1;
|
2002-10-29 21:56:30 +01:00
|
|
|
CREATE TABLE t1 (
|
|
|
|
|
d datetime default NULL
|
2003-12-10 05:31:42 +01:00
|
|
|
) ENGINE=MyISAM;
|
2002-10-29 21:56:30 +01:00
|
|
|
INSERT INTO t1 VALUES ('2002-10-24 14:50:32'),('2002-10-24 14:50:33'),('2002-10-24 14:50:34'),('2002-10-24 14:50:34'),('2002-10-24 14:50:34'),('2002-10-24 14:50:35'),('2002-10-24 14:50:35'),('2002-10-24 14:50:35'),('2002-10-24 14:50:35'),('2002-10-24 14:50:36'),('2002-10-24 14:50:36'),('2002-10-24 14:50:36'),('2002-10-24 14:50:36'),('2002-10-24 14:50:37'),('2002-10-24 14:50:37'),('2002-10-24 14:50:37'),('2002-10-24 14:50:37'),('2002-10-24 14:50:38'),('2002-10-24 14:50:38'),('2002-10-24 14:50:38'),('2002-10-24 14:50:39'),('2002-10-24 14:50:39'),('2002-10-24 14:50:39'),('2002-10-24 14:50:39'),('2002-10-24 14:50:40'),('2002-10-24 14:50:40'),('2002-10-24 14:50:40');
|
|
|
|
|
flush status;
|
|
|
|
|
select * from t1 group by d;
|
|
|
|
|
d
|
|
|
|
|
2002-10-24 14:50:32
|
|
|
|
|
2002-10-24 14:50:33
|
|
|
|
|
2002-10-24 14:50:34
|
|
|
|
|
2002-10-24 14:50:35
|
|
|
|
|
2002-10-24 14:50:36
|
|
|
|
|
2002-10-24 14:50:37
|
|
|
|
|
2002-10-24 14:50:38
|
|
|
|
|
2002-10-24 14:50:39
|
|
|
|
|
2002-10-24 14:50:40
|
|
|
|
|
show status like "created_tmp%tables";
|
|
|
|
|
Variable_name Value
|
2005-02-23 13:15:36 +01:00
|
|
|
Created_tmp_disk_tables 0
|
2006-06-20 12:20:32 +02:00
|
|
|
Created_tmp_tables 1
|
2002-10-29 21:56:30 +01:00
|
|
|
drop table t1;
|
2005-09-22 02:23:07 +02:00
|
|
|
create temporary table v1 as select 'This is temp. table' A;
|
|
|
|
|
create view v1 as select 'This is view' A;
|
|
|
|
|
select * from v1;
|
2005-04-25 02:00:35 +02:00
|
|
|
A
|
|
|
|
|
This is temp. table
|
2005-09-22 02:23:07 +02:00
|
|
|
show create table v1;
|
2005-04-25 02:00:35 +02:00
|
|
|
Table Create Table
|
2005-09-22 02:23:07 +02:00
|
|
|
v1 CREATE TEMPORARY TABLE `v1` (
|
2006-02-22 10:09:59 +01:00
|
|
|
`A` varchar(19) NOT NULL DEFAULT ''
|
2005-04-25 02:00:35 +02:00
|
|
|
) ENGINE=MyISAM DEFAULT CHARSET=latin1
|
2005-09-22 02:23:07 +02:00
|
|
|
show create view v1;
|
Patch for the following bugs:
- BUG#11986: Stored routines and triggers can fail if the code
has a non-ascii symbol
- BUG#16291: mysqldump corrupts string-constants with non-ascii-chars
- BUG#19443: INFORMATION_SCHEMA does not support charsets properly
- BUG#21249: Character set of SP-var can be ignored
- BUG#25212: Character set of string constant is ignored (stored routines)
- BUG#25221: Character set of string constant is ignored (triggers)
There were a few general problems that caused these bugs:
1. Character set information of the original (definition) query for views,
triggers, stored routines and events was lost.
2. mysqldump output query in client character set, which can be
inappropriate to encode definition-query.
3. INFORMATION_SCHEMA used strings with mixed encodings to display object
definition;
1. No query-definition-character set.
In order to compile query into execution code, some extra data (such as
environment variables or the database character set) is used. The problem
here was that this context was not preserved. So, on the next load it can
differ from the original one, thus the result will be different.
The context contains the following data:
- client character set;
- connection collation (character set and collation);
- collation of the owner database;
The fix is to store this context and use it each time we parse (compile)
and execute the object (stored routine, trigger, ...).
2. Wrong mysqldump-output.
The original query can contain several encodings (by means of character set
introducers). The problem here was that we tried to convert original query
to the mysqldump-client character set.
Moreover, we stored queries in different character sets for different
objects (views, for one, used UTF8, triggers used original character set).
The solution is
- to store definition queries in the original character set;
- to change SHOW CREATE statement to output definition query in the
binary character set (i.e. without any conversion);
- introduce SHOW CREATE TRIGGER statement;
- to dump special statements to switch the context to the original one
before dumping and restore it afterwards.
Note, in order to preserve the database collation at the creation time,
additional ALTER DATABASE might be used (to temporary switch the database
collation back to the original value). In this case, ALTER DATABASE
privilege will be required. This is a backward-incompatible change.
3. INFORMATION_SCHEMA showed non-UTF8 strings
The fix is to generate UTF8-query during the parsing, store it in the object
and show it in the INFORMATION_SCHEMA.
Basically, the idea is to create a copy of the original query convert it to
UTF8. Character set introducers are removed and all text literals are
converted to UTF8.
This UTF8 query is intended to provide user-readable output. It must not be
used to recreate the object. Specialized SHOW CREATE statements should be
used for this.
The reason for this limitation is the following: the original query can
contain symbols from several character sets (by means of character set
introducers).
Example:
- original query:
CREATE VIEW v1 AS SELECT _cp1251 'Hello' AS c1;
- UTF8 query (for INFORMATION_SCHEMA):
CREATE VIEW v1 AS SELECT 'Hello' AS c1;
2007-06-28 19:34:54 +02:00
|
|
|
View Create View character_set_client collation_connection
|
|
|
|
|
v1 CREATE ALGORITHM=UNDEFINED DEFINER=`root`@`localhost` SQL SECURITY DEFINER VIEW `v1` AS select _latin1'This is view' AS `A` latin1 latin1_swedish_ci
|
2005-09-22 02:23:07 +02:00
|
|
|
drop view v1;
|
|
|
|
|
select * from v1;
|
2005-04-25 02:00:35 +02:00
|
|
|
A
|
|
|
|
|
This is temp. table
|
2005-09-22 02:23:07 +02:00
|
|
|
create view v1 as select 'This is view again' A;
|
|
|
|
|
select * from v1;
|
2005-04-25 02:00:35 +02:00
|
|
|
A
|
|
|
|
|
This is temp. table
|
2005-09-22 02:23:07 +02:00
|
|
|
drop table v1;
|
|
|
|
|
select * from v1;
|
2005-04-25 02:00:35 +02:00
|
|
|
A
|
|
|
|
|
This is view again
|
2005-09-22 02:23:07 +02:00
|
|
|
drop view v1;
|
2005-03-02 04:05:48 +01:00
|
|
|
create table t1 (a int, b int, index(a), index(b));
|
|
|
|
|
create table t2 (c int auto_increment, d varchar(255), primary key (c));
|
|
|
|
|
insert into t1 values (3,1),(3,2);
|
|
|
|
|
insert into t2 values (NULL, 'foo'), (NULL, 'bar');
|
|
|
|
|
select d, c from t1 left join t2 on b = c where a = 3 order by d;
|
|
|
|
|
d c
|
|
|
|
|
bar 2
|
|
|
|
|
foo 1
|
|
|
|
|
drop table t1, t2;
|
2006-08-29 14:59:20 +02:00
|
|
|
DROP TABLE IF EXISTS t1;
|
|
|
|
|
CREATE TABLE t1 (i INT);
|
|
|
|
|
LOCK TABLE t1 WRITE;
|
|
|
|
|
CREATE TEMPORARY TABLE t1 (i INT);
|
|
|
|
|
The following command should not block
|
|
|
|
|
DROP TEMPORARY TABLE t1;
|
|
|
|
|
DROP TABLE t1;
|
|
|
|
|
CREATE TABLE t1 (i INT);
|
|
|
|
|
CREATE TEMPORARY TABLE t2 (i INT);
|
|
|
|
|
DROP TEMPORARY TABLE t2, t1;
|
|
|
|
|
ERROR 42S02: Unknown table 't1'
|
|
|
|
|
SELECT * FROM t2;
|
|
|
|
|
ERROR 42S02: Table 'test.t2' doesn't exist
|
|
|
|
|
SELECT * FROM t1;
|
|
|
|
|
i
|
|
|
|
|
DROP TABLE t1;
|
|
|
|
|
End of 4.1 tests.
|
Bug #24791: Union with AVG-groups generates wrong results
The problem in this bug is when we create temporary tables. When
temporary tables are created for unions, there is some
inferrence being carried out regarding the type of the column.
Whenever this column type is inferred to be REAL (i.e. FLOAT or
DOUBLE), MySQL will always try to maintain exact precision, and
if that is not possible (there are hardware limits, since FLOAT
and DOUBLE are stored as approximate values) will switch to
using approximate values. The problem here is that at this point
the information about number of significant digits is not
available. Furthermore, the number of significant digits should
be increased for the AVG function, however, this was not properly
handled. There are 4 parts to the problem:
#1: DOUBLE and FLOAT fields don't display their proper display
lengths in max_display_length(). This is hard-coded as 53 for
DOUBLE and 24 for FLOAT. Now changed to instead return the
field_length.
#2: Type holders for temporary tables do not preserve the
max_length of the Item's from which they are created, and is
instead reverted to the 53 and 24 from above. This causes
*all* fields to get non-fixed significant digits.
#3: AVG function does not update max_length (display length)
when updating number of decimals.
#4: The function that switches to non-fixed number of
significant digits should use DBL_DIG + 2 or FLT_DIG + 2 as
cut-off values (Since fixed precision does not use the 'e'
notation)
Of these points, #1 is the controversial one, but this
change is preferred and has been cleared with Monty. The
function causes quite a few unit tests to blow up and they had
to b changed, but each one is annotated and motivated. We
frequently see the magical 53 and 24 give way to more relevant
numbers.
2007-03-22 10:56:47 +01:00
|
|
|
CREATE TABLE t1 ( c FLOAT( 20, 14 ) );
|
|
|
|
|
INSERT INTO t1 VALUES( 12139 );
|
|
|
|
|
CREATE TABLE t2 ( c FLOAT(30,18) );
|
|
|
|
|
INSERT INTO t2 VALUES( 123456 );
|
|
|
|
|
SELECT AVG( c ) FROM t1 UNION SELECT 1;
|
|
|
|
|
AVG( c )
|
|
|
|
|
12139
|
|
|
|
|
1
|
|
|
|
|
SELECT 1 UNION SELECT AVG( c ) FROM t1;
|
|
|
|
|
1
|
|
|
|
|
1
|
|
|
|
|
12139
|
|
|
|
|
SELECT 1 UNION SELECT * FROM t2 UNION SELECT 1;
|
|
|
|
|
1
|
|
|
|
|
1
|
|
|
|
|
123456
|
|
|
|
|
SELECT c/1 FROM t1 UNION SELECT 1;
|
|
|
|
|
c/1
|
|
|
|
|
12139
|
|
|
|
|
1
|
|
|
|
|
DROP TABLE t1, t2;
|
2005-11-23 21:45:02 +01:00
|
|
|
create temporary table t1 (a int);
|
|
|
|
|
insert into t1 values (4711);
|
|
|
|
|
select * from t1;
|
|
|
|
|
a
|
|
|
|
|
4711
|
|
|
|
|
truncate t1;
|
|
|
|
|
insert into t1 values (42);
|
|
|
|
|
select * from t1;
|
|
|
|
|
a
|
|
|
|
|
42
|
|
|
|
|
drop table t1;
|