mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-09-13 20:19:44 +02:00
1763a7c1ea
after trying to resolve the item as an input-column name. This allows us to be compliant with the SQL92 spec for queries that fall within the spec, while still accepting the same out-of-spec queries as 6.5 did. You'll only lose if there is an output column name that is the same as an input column name, but doesn't refer to the same value. 7.0 will interpret such a GROUP BY spec differently than 6.5 did. No way around that, because 6.5 was clearly not spec compliant.
137 lines
3.4 KiB
Plaintext
137 lines
3.4 KiB
Plaintext
--
|
|
-- NUMEROLOGY
|
|
-- Test various combinations of numeric types and functions.
|
|
--
|
|
--
|
|
-- Test implicit type conversions
|
|
-- This fails for Postgres v6.1 (and earlier?)
|
|
-- so let's try explicit conversions for now - tgl 97/05/07
|
|
--
|
|
CREATE TABLE TEMP_FLOAT (f1 FLOAT8);
|
|
INSERT INTO TEMP_FLOAT (f1)
|
|
SELECT float8(f1) FROM INT4_TBL;
|
|
INSERT INTO TEMP_FLOAT (f1)
|
|
SELECT float8(f1) FROM INT2_TBL;
|
|
SELECT '' AS ten, f1 FROM TEMP_FLOAT
|
|
ORDER BY f1;
|
|
ten | f1
|
|
-----+-------------
|
|
| -2147483647
|
|
| -123456
|
|
| -32767
|
|
| -1234
|
|
| 0
|
|
| 0
|
|
| 1234
|
|
| 32767
|
|
| 123456
|
|
| 2147483647
|
|
(10 rows)
|
|
|
|
-- int4
|
|
CREATE TABLE TEMP_INT4 (f1 INT4);
|
|
INSERT INTO TEMP_INT4 (f1)
|
|
SELECT int4(f1) FROM FLOAT8_TBL
|
|
WHERE (f1 > -2147483647) AND (f1 < 2147483647);
|
|
INSERT INTO TEMP_INT4 (f1)
|
|
SELECT int4(f1) FROM INT2_TBL;
|
|
SELECT '' AS nine, f1 FROM TEMP_INT4
|
|
ORDER BY f1;
|
|
nine | f1
|
|
------+--------
|
|
| -32767
|
|
| -1234
|
|
| -1004
|
|
| -35
|
|
| 0
|
|
| 0
|
|
| 0
|
|
| 1234
|
|
| 32767
|
|
(9 rows)
|
|
|
|
-- int2
|
|
CREATE TABLE TEMP_INT2 (f1 INT2);
|
|
INSERT INTO TEMP_INT2 (f1)
|
|
SELECT int2(f1) FROM FLOAT8_TBL
|
|
WHERE (f1 >= -32767) AND (f1 <= 32767);
|
|
INSERT INTO TEMP_INT2 (f1)
|
|
SELECT int2(f1) FROM INT4_TBL
|
|
WHERE (f1 >= -32767) AND (f1 <= 32767);
|
|
SELECT '' AS five, f1 FROM TEMP_INT2
|
|
ORDER BY f1;
|
|
five | f1
|
|
------+-------
|
|
| -1004
|
|
| -35
|
|
| 0
|
|
| 0
|
|
| 0
|
|
(5 rows)
|
|
|
|
--
|
|
-- Group-by combinations
|
|
--
|
|
CREATE TABLE TEMP_GROUP (f1 INT4, f2 INT4, f3 FLOAT8);
|
|
INSERT INTO TEMP_GROUP
|
|
SELECT 1, (- i.f1), (- f.f1)
|
|
FROM INT4_TBL i, FLOAT8_TBL f;
|
|
INSERT INTO TEMP_GROUP
|
|
SELECT 2, i.f1, f.f1
|
|
FROM INT4_TBL i, FLOAT8_TBL f;
|
|
SELECT DISTINCT f1 AS two FROM TEMP_GROUP;
|
|
two
|
|
-----
|
|
1
|
|
2
|
|
(2 rows)
|
|
|
|
SELECT f1 AS two, max(f3) AS max_float, min(f3) as min_float
|
|
FROM TEMP_GROUP
|
|
GROUP BY f1
|
|
ORDER BY two, max_float, min_float;
|
|
two | max_float | min_float
|
|
-----+----------------------+-----------------------
|
|
1 | 1.2345678901234e+200 | 0
|
|
2 | 0 | -1.2345678901234e+200
|
|
(2 rows)
|
|
|
|
-- GROUP BY a result column name is not legal per SQL92, but we accept it
|
|
-- anyway (if the name is not the name of any column exposed by FROM).
|
|
SELECT f1 AS two, max(f3) AS max_float, min(f3) AS min_float
|
|
FROM TEMP_GROUP
|
|
GROUP BY two
|
|
ORDER BY two, max_float, min_float;
|
|
two | max_float | min_float
|
|
-----+----------------------+-----------------------
|
|
1 | 1.2345678901234e+200 | 0
|
|
2 | 0 | -1.2345678901234e+200
|
|
(2 rows)
|
|
|
|
SELECT f1 AS two, (max(f3) + 1) AS max_plus_1, (min(f3) - 1) AS min_minus_1
|
|
FROM TEMP_GROUP
|
|
GROUP BY f1
|
|
ORDER BY two, min_minus_1;
|
|
two | max_plus_1 | min_minus_1
|
|
-----+----------------------+-----------------------
|
|
1 | 1.2345678901234e+200 | -1
|
|
2 | 1 | -1.2345678901234e+200
|
|
(2 rows)
|
|
|
|
SELECT f1 AS two,
|
|
max(f2) + min(f2) AS max_plus_min,
|
|
min(f3) - 1 AS min_minus_1
|
|
FROM TEMP_GROUP
|
|
GROUP BY f1
|
|
ORDER BY two, min_minus_1;
|
|
two | max_plus_min | min_minus_1
|
|
-----+--------------+-----------------------
|
|
1 | 0 | -1
|
|
2 | 0 | -1.2345678901234e+200
|
|
(2 rows)
|
|
|
|
DROP TABLE TEMP_INT2;
|
|
DROP TABLE TEMP_INT4;
|
|
DROP TABLE TEMP_FLOAT;
|
|
DROP TABLE TEMP_GROUP;
|