mirror of
				https://github.com/MariaDB/server.git
				synced 2025-10-27 05:56:07 +03:00 
			
		
		
		
	(4.1 version, with post-review fixes) The fix for another Bug (6439) limited FROM_UNIXTIME() to TIMESTAMP_MAX_VALUE which is 2145916799 or 2037-12-01 23:59:59 GMT, however unix timestamp in general is not considered to be limited by this value. All dates up to power(2,31)-1 are valid. This patch extends allowed TIMESTAMP range so, that max TIMESTAMP value is power(2,31)-1. It also corrects FROM_UNIXTIME() and UNIX_TIMESTAMP() functions, so that max allowed UNIX_TIMESTAMP() is power(2,31)-1. FROM_UNIXTIME() is fixed accordingly to allow conversion of dates up to 2038-01-19 03:14:07 UTC. The patch also fixes CONVERT_TZ() function to allow extended range of dates. The main problem solved in the patch is possible overflows of variables, used in broken-time representation to time_t conversion (required for UNIX_TIMESTAMP). acinclude.m4: Add new macro to check time_t range configure.in: Call the macro to check time_t range include/my_time.h: Move time-related defines to proper place. Add a function to perform a rough check if a TIMESTAMP value fits into the boundaries. Note: it is defined as "static inline", as otherwise libmysql won't compile (due to the way how gcc handles "inline" directive). mysql-test/r/func_time.result: Update test result mysql-test/r/timezone.result: Update test result mysql-test/r/timezone2.result: Update test result mysql-test/t/func_time.test: Add test for Bug#9191 and update test to be consistent with new TIMESTAMP boundaries mysql-test/t/timezone.test: Update old tests to be consistent with new TIMESTAMP boundaries mysql-test/t/timezone2.test: Update tests for convert_tz to be consistent with new TIMESTAMP boundaries sql/item_timefunc.cc: Fix convert_tz to allow dates from the new (extended) TIMESTAMP range sql/mysql_priv.h: Move time handling defaults to my_time.h sql-common/my_time.c: Because of increased TIMESTAMP_MAX_VALUE overflows in my_system_gmt_sec() became possible. Here we make it safe against the overflows by stepping back from the boundary dates which are likely to trigger them. sql/time.cc: Update TIME_to_timestamp to allow conversion of extended date range sql/tztime.cc: Fix new (4.1) implementation of broken-down time representation to time_t conversion routine to avoid overflows during conversion of boundary dates mysql-test/r/timezone4.result: New BitKeeper file ``mysql-test/r/timezone4.result'' mysql-test/t/timezone4-master.opt: New BitKeeper file ``mysql-test/t/timezone4-master.opt'' mysql-test/t/timezone4.test: New BitKeeper file ``mysql-test/t/timezone4.test''
		
			
				
	
	
		
			48 lines
		
	
	
		
			1.8 KiB
		
	
	
	
		
			Plaintext
		
	
	
	
	
	
			
		
		
	
	
			48 lines
		
	
	
		
			1.8 KiB
		
	
	
	
		
			Plaintext
		
	
	
	
	
	
| DROP TABLE IF EXISTS t1;
 | |
| show variables like "system_time_zone";
 | |
| Variable_name	Value
 | |
| system_time_zone	MET
 | |
| select @a:=FROM_UNIXTIME(1);
 | |
| @a:=FROM_UNIXTIME(1)
 | |
| 1970-01-01 01:00:01
 | |
| select unix_timestamp(@a);
 | |
| unix_timestamp(@a)
 | |
| 1
 | |
| CREATE TABLE t1 (ts int);
 | |
| INSERT INTO t1 (ts) VALUES (Unix_timestamp('2002-10-27 01:00'));
 | |
| INSERT INTO t1 (ts) VALUES (Unix_timestamp('2002-10-27 02:00'));
 | |
| INSERT INTO t1 (ts) VALUES (Unix_timestamp('2002-10-27 03:00'));
 | |
| INSERT INTO t1 (ts) VALUES (Unix_timestamp('2002-10-27 02:00'));
 | |
| INSERT INTO t1 (ts) VALUES (Unix_timestamp('2002-10-27 01:00'));
 | |
| INSERT INTO t1 (ts) VALUES (Unix_timestamp('2002-10-27 02:00'));
 | |
| INSERT INTO t1 (ts) VALUES (Unix_timestamp('2003-03-30 02:59:59'));
 | |
| INSERT INTO t1 (ts) VALUES (Unix_timestamp('2003-03-30 03:00:00'));
 | |
| INSERT INTO t1 (ts) VALUES (Unix_timestamp('2003-03-30 03:59:59'));
 | |
| INSERT INTO t1 (ts) VALUES (Unix_timestamp('2003-03-30 04:00:01'));
 | |
| SELECT ts,from_unixtime(ts) FROM t1;
 | |
| ts	from_unixtime(ts)
 | |
| 1035673200	2002-10-27 01:00:00
 | |
| 1035680400	2002-10-27 02:00:00
 | |
| 1035684000	2002-10-27 03:00:00
 | |
| 1035680400	2002-10-27 02:00:00
 | |
| 1035673200	2002-10-27 01:00:00
 | |
| 1035680400	2002-10-27 02:00:00
 | |
| 1048986000	2003-03-30 03:00:00
 | |
| 1048986000	2003-03-30 03:00:00
 | |
| 1048989599	2003-03-30 03:59:59
 | |
| 1048989601	2003-03-30 04:00:01
 | |
| DROP TABLE t1;
 | |
| CREATE TABLE t1 (ts timestamp);
 | |
| INSERT INTO t1 (ts) VALUES ('2003-03-30 01:59:59'),
 | |
| ('2003-03-30 02:59:59'),
 | |
| ('2003-03-30 03:00:00');
 | |
| Warnings:
 | |
| Warning	1299	Invalid TIMESTAMP value in column 'ts' at row 2
 | |
| DROP TABLE t1;
 | |
| select unix_timestamp('1970-01-01 01:00:00'), 
 | |
| unix_timestamp('1970-01-01 01:00:01'),
 | |
| unix_timestamp('2038-01-19 04:14:07'),
 | |
| unix_timestamp('2038-01-19 04:14:08');
 | |
| unix_timestamp('1970-01-01 01:00:00')	unix_timestamp('1970-01-01 01:00:01')	unix_timestamp('2038-01-19 04:14:07')	unix_timestamp('2038-01-19 04:14:08')
 | |
| 0	1	2147483647	0
 |