2000-09-12 07:42:20 +02:00
|
|
|
--
|
|
|
|
-- TIME
|
|
|
|
--
|
2001-10-03 07:29:27 +02:00
|
|
|
CREATE TABLE TIME_TBL (f1 time(2));
|
2001-09-28 10:00:11 +02:00
|
|
|
INSERT INTO TIME_TBL VALUES ('00:00');
|
|
|
|
INSERT INTO TIME_TBL VALUES ('01:00');
|
2003-01-31 02:08:08 +01:00
|
|
|
-- as of 7.4, timezone spec should be accepted and ignored
|
|
|
|
INSERT INTO TIME_TBL VALUES ('02:03 PST');
|
|
|
|
INSERT INTO TIME_TBL VALUES ('11:59 EDT');
|
2001-09-28 10:00:11 +02:00
|
|
|
INSERT INTO TIME_TBL VALUES ('12:00');
|
|
|
|
INSERT INTO TIME_TBL VALUES ('12:01');
|
|
|
|
INSERT INTO TIME_TBL VALUES ('23:59');
|
|
|
|
INSERT INTO TIME_TBL VALUES ('11:59:59.99 PM');
|
2006-07-06 03:46:38 +02:00
|
|
|
INSERT INTO TIME_TBL VALUES ('2003-03-07 15:36:39 America/New_York');
|
|
|
|
INSERT INTO TIME_TBL VALUES ('2003-07-07 15:36:39 America/New_York');
|
|
|
|
-- this should fail (the timezone offset is not known)
|
|
|
|
INSERT INTO TIME_TBL VALUES ('15:36:39 America/New_York');
|
|
|
|
ERROR: invalid input syntax for type time: "15:36:39 America/New_York"
|
2008-09-01 22:42:46 +02:00
|
|
|
LINE 1: INSERT INTO TIME_TBL VALUES ('15:36:39 America/New_York');
|
|
|
|
^
|
2001-09-28 10:00:11 +02:00
|
|
|
SELECT f1 AS "Time" FROM TIME_TBL;
|
2001-10-03 07:29:27 +02:00
|
|
|
Time
|
|
|
|
-------------
|
2001-09-28 10:00:11 +02:00
|
|
|
00:00:00
|
|
|
|
01:00:00
|
|
|
|
02:03:00
|
|
|
|
11:59:00
|
|
|
|
12:00:00
|
|
|
|
12:01:00
|
|
|
|
23:59:00
|
2001-10-03 07:29:27 +02:00
|
|
|
23:59:59.99
|
2006-07-06 03:46:38 +02:00
|
|
|
15:36:39
|
|
|
|
15:36:39
|
|
|
|
(10 rows)
|
2000-09-12 07:42:20 +02:00
|
|
|
|
|
|
|
SELECT f1 AS "Three" FROM TIME_TBL WHERE f1 < '05:06:07';
|
|
|
|
Three
|
|
|
|
----------
|
|
|
|
00:00:00
|
|
|
|
01:00:00
|
|
|
|
02:03:00
|
|
|
|
(3 rows)
|
|
|
|
|
|
|
|
SELECT f1 AS "Five" FROM TIME_TBL WHERE f1 > '05:06:07';
|
2001-10-03 07:29:27 +02:00
|
|
|
Five
|
|
|
|
-------------
|
2000-09-12 07:42:20 +02:00
|
|
|
11:59:00
|
|
|
|
12:00:00
|
|
|
|
12:01:00
|
|
|
|
23:59:00
|
2001-10-03 07:29:27 +02:00
|
|
|
23:59:59.99
|
2006-07-06 03:46:38 +02:00
|
|
|
15:36:39
|
|
|
|
15:36:39
|
|
|
|
(7 rows)
|
2000-09-12 07:42:20 +02:00
|
|
|
|
|
|
|
SELECT f1 AS "None" FROM TIME_TBL WHERE f1 < '00:00';
|
|
|
|
None
|
|
|
|
------
|
|
|
|
(0 rows)
|
|
|
|
|
|
|
|
SELECT f1 AS "Eight" FROM TIME_TBL WHERE f1 >= '00:00';
|
2001-10-03 07:29:27 +02:00
|
|
|
Eight
|
|
|
|
-------------
|
2000-09-12 07:42:20 +02:00
|
|
|
00:00:00
|
|
|
|
01:00:00
|
|
|
|
02:03:00
|
|
|
|
11:59:00
|
|
|
|
12:00:00
|
|
|
|
12:01:00
|
|
|
|
23:59:00
|
2001-10-03 07:29:27 +02:00
|
|
|
23:59:59.99
|
2006-07-06 03:46:38 +02:00
|
|
|
15:36:39
|
|
|
|
15:36:39
|
|
|
|
(10 rows)
|
2000-09-12 07:42:20 +02:00
|
|
|
|
|
|
|
--
|
|
|
|
-- TIME simple math
|
|
|
|
--
|
2000-12-03 15:51:12 +01:00
|
|
|
-- We now make a distinction between time and intervals,
|
|
|
|
-- and adding two times together makes no sense at all.
|
|
|
|
-- Leave in one query to show that it is rejected,
|
|
|
|
-- and do the rest of the testing in horology.sql
|
|
|
|
-- where we do mixed-type arithmetic. - thomas 2000-12-02
|
|
|
|
SELECT f1 + time '00:01' AS "Illegal" FROM TIME_TBL;
|
2003-07-04 04:51:34 +02:00
|
|
|
ERROR: operator is not unique: time without time zone + time without time zone
|
2006-03-14 23:48:25 +01:00
|
|
|
LINE 1: SELECT f1 + time '00:01' AS "Illegal" FROM TIME_TBL;
|
|
|
|
^
|
Wording cleanup for error messages. Also change can't -> cannot.
Standard English uses "may", "can", and "might" in different ways:
may - permission, "You may borrow my rake."
can - ability, "I can lift that log."
might - possibility, "It might rain today."
Unfortunately, in conversational English, their use is often mixed, as
in, "You may use this variable to do X", when in fact, "can" is a better
choice. Similarly, "It may crash" is better stated, "It might crash".
2007-02-01 20:10:30 +01:00
|
|
|
HINT: Could not choose a best candidate operator. You might need to add explicit type casts.
|