blob: 65c77502de81503dc4cb6f1238813823265df8ad (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
|
<sql-statement>
--
-- TIME
--
CREATE TABLE TIME_TBL (f1 time(2));
</sql-statement>
<sql-statement>
INSERT INTO TIME_TBL VALUES ('00:00');
</sql-statement>
<sql-statement>
INSERT INTO TIME_TBL VALUES ('01:00');
</sql-statement>
<sql-statement>
-- as of 7.4, timezone spec should be accepted and ignored
INSERT INTO TIME_TBL VALUES ('02:03 PST');
</sql-statement>
-stdin-:<main>: Fatal: Execution
-stdin-:<main>:1:1: Fatal: Execution of node: YtFill!
-- as of 7.4, timezone spec should be accepted and ignored
^
-stdin-:<main>:1:1: Fatal: ERROR: invalid input syntax for type time: "02:03 PST"
-- as of 7.4, timezone spec should be accepted and ignored
^
<sql-statement>
INSERT INTO TIME_TBL VALUES ('11:59 EDT');
</sql-statement>
-stdin-:<main>: Fatal: Execution
-stdin-:<main>:1:1: Fatal: Execution of node: YtFill!
INSERT INTO TIME_TBL VALUES ('11:59 EDT');
^
-stdin-:<main>:1:1: Fatal: ERROR: invalid input syntax for type time: "11:59 EDT"
INSERT INTO TIME_TBL VALUES ('11:59 EDT');
^
<sql-statement>
INSERT INTO TIME_TBL VALUES ('12:00');
</sql-statement>
<sql-statement>
INSERT INTO TIME_TBL VALUES ('12:01');
</sql-statement>
<sql-statement>
INSERT INTO TIME_TBL VALUES ('23:59');
</sql-statement>
<sql-statement>
INSERT INTO TIME_TBL VALUES ('11:59:59.99 PM');
</sql-statement>
<sql-statement>
INSERT INTO TIME_TBL VALUES ('2003-03-07 15:36:39 America/New_York');
</sql-statement>
-stdin-:<main>: Fatal: Execution
-stdin-:<main>:1:1: Fatal: Execution of node: YtFill!
INSERT INTO TIME_TBL VALUES ('2003-03-07 15:36:39 America/New_York');
^
-stdin-:<main>:1:1: Fatal: ERROR: time zone "america/new_york" not recognized
INSERT INTO TIME_TBL VALUES ('2003-03-07 15:36:39 America/New_York');
^
<sql-statement>
INSERT INTO TIME_TBL VALUES ('2003-07-07 15:36:39 America/New_York');
</sql-statement>
-stdin-:<main>: Fatal: Execution
-stdin-:<main>:1:1: Fatal: Execution of node: YtFill!
INSERT INTO TIME_TBL VALUES ('2003-07-07 15:36:39 America/New_York');
^
-stdin-:<main>:1:1: Fatal: ERROR: time zone "america/new_york" not recognized
INSERT INTO TIME_TBL VALUES ('2003-07-07 15:36:39 America/New_York');
^
<sql-statement>
-- this should fail (the timezone offset is not known)
INSERT INTO TIME_TBL VALUES ('15:36:39 America/New_York');
</sql-statement>
-stdin-:<main>: Fatal: Execution
-stdin-:<main>:1:1: Fatal: Execution of node: YtFill!
-- this should fail (the timezone offset is not known)
^
-stdin-:<main>:1:1: Fatal: ERROR: time zone "america/new_york" not recognized
-- this should fail (the timezone offset is not known)
^
<sql-statement>
SELECT f1 AS "Time" FROM TIME_TBL;
</sql-statement>
<sql-statement>
SELECT f1 AS "Three" FROM TIME_TBL WHERE f1 < '05:06:07';
</sql-statement>
<sql-statement>
SELECT f1 AS "Five" FROM TIME_TBL WHERE f1 > '05:06:07';
</sql-statement>
<sql-statement>
SELECT f1 AS "None" FROM TIME_TBL WHERE f1 < '00:00';
</sql-statement>
<sql-statement>
SELECT f1 AS "Eight" FROM TIME_TBL WHERE f1 >= '00:00';
</sql-statement>
<sql-statement>
-- Check edge cases
SELECT '23:59:59.999999'::time;
</sql-statement>
<sql-statement>
SELECT '23:59:59.9999999'::time; -- rounds up
</sql-statement>
<sql-statement>
SELECT '23:59:60'::time; -- rounds up
</sql-statement>
<sql-statement>
SELECT '24:00:00'::time; -- allowed
</sql-statement>
<sql-statement>
SELECT '24:00:00.01'::time; -- not allowed
</sql-statement>
-stdin-:<main>: Fatal: Execution
-stdin-:<main>:1:1: Fatal: Execution of node: Result
SELECT '24:00:00.01'::time; -- not allowed
^
-stdin-:<main>:1:1: Fatal: ERROR: date/time field value out of range: "24:00:00.01"
SELECT '24:00:00.01'::time; -- not allowed
^
<sql-statement>
SELECT '23:59:60.01'::time; -- not allowed
</sql-statement>
-stdin-:<main>: Fatal: Execution
-stdin-:<main>:1:1: Fatal: Execution of node: Result
SELECT '23:59:60.01'::time; -- not allowed
^
-stdin-:<main>:1:1: Fatal: ERROR: date/time field value out of range: "23:59:60.01"
SELECT '23:59:60.01'::time; -- not allowed
^
<sql-statement>
SELECT '24:01:00'::time; -- not allowed
</sql-statement>
-stdin-:<main>: Fatal: Execution
-stdin-:<main>:1:1: Fatal: Execution of node: Result
SELECT '24:01:00'::time; -- not allowed
^
-stdin-:<main>:1:1: Fatal: ERROR: date/time field value out of range: "24:01:00"
SELECT '24:01:00'::time; -- not allowed
^
<sql-statement>
SELECT '25:00:00'::time; -- not allowed
</sql-statement>
-stdin-:<main>: Fatal: Execution
-stdin-:<main>:1:1: Fatal: Execution of node: Result
SELECT '25:00:00'::time; -- not allowed
^
-stdin-:<main>:1:1: Fatal: ERROR: date/time field value out of range: "25:00:00"
SELECT '25:00:00'::time; -- not allowed
^
<sql-statement>
--
-- TIME simple math
--
-- 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;
</sql-statement>
<sql-statement>
--
-- test EXTRACT
--
SELECT EXTRACT(MICROSECOND FROM TIME '2020-05-26 13:30:25.575401');
</sql-statement>
<sql-statement>
SELECT EXTRACT(MILLISECOND FROM TIME '2020-05-26 13:30:25.575401');
</sql-statement>
<sql-statement>
SELECT EXTRACT(SECOND FROM TIME '2020-05-26 13:30:25.575401');
</sql-statement>
<sql-statement>
SELECT EXTRACT(MINUTE FROM TIME '2020-05-26 13:30:25.575401');
</sql-statement>
<sql-statement>
SELECT EXTRACT(HOUR FROM TIME '2020-05-26 13:30:25.575401');
</sql-statement>
<sql-statement>
SELECT EXTRACT(DAY FROM TIME '2020-05-26 13:30:25.575401'); -- error
</sql-statement>
-stdin-:<main>: Fatal: Execution
-stdin-:<main>:1:1: Fatal: Execution of node: Result
SELECT EXTRACT(DAY FROM TIME '2020-05-26 13:30:25.575401'); -- error
^
-stdin-:<main>:1:1: Fatal: ERROR: "time" units "day" not recognized
SELECT EXTRACT(DAY FROM TIME '2020-05-26 13:30:25.575401'); -- error
^
<sql-statement>
SELECT EXTRACT(FORTNIGHT FROM TIME '2020-05-26 13:30:25.575401'); -- error
</sql-statement>
-stdin-:<main>: Fatal: Execution
-stdin-:<main>:1:1: Fatal: Execution of node: Result
SELECT EXTRACT(FORTNIGHT FROM TIME '2020-05-26 13:30:25.575401'); -- error
^
-stdin-:<main>:1:1: Fatal: ERROR: "time" units "fortnight" not recognized
SELECT EXTRACT(FORTNIGHT FROM TIME '2020-05-26 13:30:25.575401'); -- error
^
<sql-statement>
SELECT EXTRACT(TIMEZONE FROM TIME '2020-05-26 13:30:25.575401'); -- error
</sql-statement>
-stdin-:<main>: Fatal: Execution
-stdin-:<main>:1:1: Fatal: Execution of node: Result
SELECT EXTRACT(TIMEZONE FROM TIME '2020-05-26 13:30:25.575401'); -- error
^
-stdin-:<main>:1:1: Fatal: ERROR: "time" units "timezone" not recognized
SELECT EXTRACT(TIMEZONE FROM TIME '2020-05-26 13:30:25.575401'); -- error
^
<sql-statement>
SELECT EXTRACT(EPOCH FROM TIME '2020-05-26 13:30:25.575401');
</sql-statement>
<sql-statement>
-- date_part implementation is mostly the same as extract, so only
-- test a few cases for additional coverage.
SELECT date_part('microsecond', TIME '2020-05-26 13:30:25.575401');
</sql-statement>
<sql-statement>
SELECT date_part('millisecond', TIME '2020-05-26 13:30:25.575401');
</sql-statement>
<sql-statement>
SELECT date_part('second', TIME '2020-05-26 13:30:25.575401');
</sql-statement>
<sql-statement>
SELECT date_part('epoch', TIME '2020-05-26 13:30:25.575401');
</sql-statement>
|
