1997-04-05 23:26:00 +02:00
|
|
|
--
|
2000-01-05 18:32:29 +01:00
|
|
|
-- CREATE_TYPE
|
1997-04-05 23:26:00 +02:00
|
|
|
--
|
|
|
|
|
2006-02-28 23:37:27 +01:00
|
|
|
--
|
|
|
|
-- Note: widget_in/out were created in create_function_1, without any
|
|
|
|
-- prior shell-type creation. These commands therefore complete a test
|
|
|
|
-- of the "old style" approach of making the functions first.
|
|
|
|
--
|
Major patch from Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
OK, here are a passel of patches for the geometric data types.
These add a "circle" data type, new operators and functions
for the existing data types, and change the default formats
for some of the existing types to make them consistant with
each other. Current formatting conventions (e.g. compatible
with v6.0 to allow dump/reload) are supported, but the new
conventions should be an improvement and we can eventually
drop the old conventions entirely.
For example, there are two kinds of paths (connected line segments),
open and closed, and the old format was
'(1,2,1,2,3,4)' for a closed path with two points (1,2) and (3,4)
'(0,2,1,2,3,4)' for an open path with two points (1,2) and (3,4)
Pretty arcane, huh? The new format for paths is
'((1,2),(3,4))' for a closed path with two points (1,2) and (3,4)
'[(1,2),(3,4)]' for an open path with two points (1,2) and (3,4)
For polygons, the old convention is
'(0,4,2,0,4,3)' for a triangle with points at (0,0),(4,4), and (2,3)
and the new convention is
'((0,0),(4,4),(2,3))' for a triangle with points at (0,0),(4,4), and (2,3)
Other data types which are also represented as lists of points
(e.g. boxes, line segments, and polygons) have similar representations
(they surround each point with parens).
For v6.1, any format which can be interpreted as the old style format
is decoded as such; we can remove that backwards compatibility but ugly
convention for v7.0. This will allow dump/reloads from v6.0.
These include some updates to the regression test files to change the test
for creating a data type from "circle" to "widget" to keep the test from
trashing the new builtin circle type.
1997-04-22 19:35:09 +02:00
|
|
|
CREATE TYPE widget (
|
2010-11-23 21:27:50 +01:00
|
|
|
internallength = 24,
|
Major patch from Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
OK, here are a passel of patches for the geometric data types.
These add a "circle" data type, new operators and functions
for the existing data types, and change the default formats
for some of the existing types to make them consistant with
each other. Current formatting conventions (e.g. compatible
with v6.0 to allow dump/reload) are supported, but the new
conventions should be an improvement and we can eventually
drop the old conventions entirely.
For example, there are two kinds of paths (connected line segments),
open and closed, and the old format was
'(1,2,1,2,3,4)' for a closed path with two points (1,2) and (3,4)
'(0,2,1,2,3,4)' for an open path with two points (1,2) and (3,4)
Pretty arcane, huh? The new format for paths is
'((1,2),(3,4))' for a closed path with two points (1,2) and (3,4)
'[(1,2),(3,4)]' for an open path with two points (1,2) and (3,4)
For polygons, the old convention is
'(0,4,2,0,4,3)' for a triangle with points at (0,0),(4,4), and (2,3)
and the new convention is
'((0,0),(4,4),(2,3))' for a triangle with points at (0,0),(4,4), and (2,3)
Other data types which are also represented as lists of points
(e.g. boxes, line segments, and polygons) have similar representations
(they surround each point with parens).
For v6.1, any format which can be interpreted as the old style format
is decoded as such; we can remove that backwards compatibility but ugly
convention for v7.0. This will allow dump/reloads from v6.0.
These include some updates to the regression test files to change the test
for creating a data type from "circle" to "widget" to keep the test from
trashing the new builtin circle type.
1997-04-22 19:35:09 +02:00
|
|
|
input = widget_in,
|
|
|
|
output = widget_out,
|
2006-12-30 22:21:56 +01:00
|
|
|
typmod_in = numerictypmodin,
|
|
|
|
typmod_out = numerictypmodout,
|
1997-04-05 23:26:00 +02:00
|
|
|
alignment = double
|
|
|
|
);
|
|
|
|
|
2010-11-23 21:27:50 +01:00
|
|
|
CREATE TYPE city_budget (
|
|
|
|
internallength = 16,
|
|
|
|
input = int44in,
|
|
|
|
output = int44out,
|
Replace the hard-wired type knowledge in TypeCategory() and IsPreferredType()
with system catalog lookups, as was foreseen to be necessary almost since
their creation. Instead put the information into two new pg_type columns,
typcategory and typispreferred. Add support for setting these when
creating a user-defined base type.
The category column is just a "char" (i.e. a poor man's enum), allowing
a crude form of user extensibility of the category list: just use an
otherwise-unused character. This seems sufficient for foreseen uses,
but we could upgrade to having an actual category catalog someday, if
there proves to be a huge demand for custom type categories.
In this patch I have attempted to hew exactly to the behavior of the
previous hardwired logic, except for introducing new type categories for
arrays, composites, and enums. In particular the default preferred state
for user-defined types remains TRUE. That seems worth revisiting, but it
should be done as a separate patch from introducing the infrastructure.
Likewise, any adjustment of the standard set of categories should be done
separately.
2008-07-30 19:05:05 +02:00
|
|
|
element = int4,
|
|
|
|
category = 'x', -- just to verify the system will take it
|
2008-07-30 21:35:13 +02:00
|
|
|
preferred = true -- ditto
|
1997-04-05 23:26:00 +02:00
|
|
|
);
|
|
|
|
|
2006-02-28 23:37:27 +01:00
|
|
|
-- Test creation and destruction of shell types
|
|
|
|
CREATE TYPE shell;
|
|
|
|
CREATE TYPE shell; -- fail, type already present
|
|
|
|
DROP TYPE shell;
|
|
|
|
DROP TYPE shell; -- fail, type not exist
|
|
|
|
|
2015-08-05 01:34:12 +02:00
|
|
|
-- also, let's leave one around for purposes of pg_dump testing
|
|
|
|
CREATE TYPE myshell;
|
|
|
|
|
2006-02-28 23:37:27 +01:00
|
|
|
--
|
2001-09-06 04:07:42 +02:00
|
|
|
-- Test type-related default values (broken in releases before PG 7.2)
|
2006-02-28 23:37:27 +01:00
|
|
|
--
|
|
|
|
-- This part of the test also exercises the "new style" approach of making
|
|
|
|
-- a shell type and then filling it in.
|
|
|
|
--
|
|
|
|
CREATE TYPE int42;
|
|
|
|
CREATE TYPE text_w_default;
|
2001-09-06 04:07:42 +02:00
|
|
|
|
2002-08-22 02:01:51 +02:00
|
|
|
-- Make dummy I/O routines using the existing internal support for int4, text
|
|
|
|
CREATE FUNCTION int42_in(cstring)
|
|
|
|
RETURNS int42
|
|
|
|
AS 'int4in'
|
2014-11-05 17:44:06 +01:00
|
|
|
LANGUAGE internal STRICT IMMUTABLE;
|
2002-08-22 02:01:51 +02:00
|
|
|
CREATE FUNCTION int42_out(int42)
|
|
|
|
RETURNS cstring
|
|
|
|
AS 'int4out'
|
2014-11-05 17:44:06 +01:00
|
|
|
LANGUAGE internal STRICT IMMUTABLE;
|
2002-08-22 02:01:51 +02:00
|
|
|
CREATE FUNCTION text_w_default_in(cstring)
|
|
|
|
RETURNS text_w_default
|
|
|
|
AS 'textin'
|
2014-11-05 17:44:06 +01:00
|
|
|
LANGUAGE internal STRICT IMMUTABLE;
|
2002-08-22 02:01:51 +02:00
|
|
|
CREATE FUNCTION text_w_default_out(text_w_default)
|
|
|
|
RETURNS cstring
|
|
|
|
AS 'textout'
|
2014-11-05 17:44:06 +01:00
|
|
|
LANGUAGE internal STRICT IMMUTABLE;
|
2002-08-22 02:01:51 +02:00
|
|
|
|
2001-09-06 04:07:42 +02:00
|
|
|
CREATE TYPE int42 (
|
|
|
|
internallength = 4,
|
2002-08-22 02:01:51 +02:00
|
|
|
input = int42_in,
|
|
|
|
output = int42_out,
|
2001-09-06 04:07:42 +02:00
|
|
|
alignment = int4,
|
|
|
|
default = 42,
|
|
|
|
passedbyvalue
|
|
|
|
);
|
|
|
|
|
|
|
|
CREATE TYPE text_w_default (
|
|
|
|
internallength = variable,
|
2002-08-22 02:01:51 +02:00
|
|
|
input = text_w_default_in,
|
|
|
|
output = text_w_default_out,
|
2001-09-06 04:07:42 +02:00
|
|
|
alignment = int4,
|
|
|
|
default = 'zippo'
|
|
|
|
);
|
|
|
|
|
|
|
|
CREATE TABLE default_test (f1 text_w_default, f2 int42);
|
|
|
|
|
|
|
|
INSERT INTO default_test DEFAULT VALUES;
|
|
|
|
|
|
|
|
SELECT * FROM default_test;
|
|
|
|
|
2002-08-15 18:36:08 +02:00
|
|
|
-- Test stand-alone composite type
|
|
|
|
|
|
|
|
CREATE TYPE default_test_row AS (f1 text_w_default, f2 int42);
|
|
|
|
|
|
|
|
CREATE FUNCTION get_default_test() RETURNS SETOF default_test_row AS '
|
|
|
|
SELECT * FROM default_test;
|
|
|
|
' LANGUAGE SQL;
|
|
|
|
|
|
|
|
SELECT * FROM get_default_test();
|
|
|
|
|
2003-11-21 23:32:49 +01:00
|
|
|
-- Test comments
|
|
|
|
COMMENT ON TYPE bad IS 'bad comment';
|
|
|
|
COMMENT ON TYPE default_test_row IS 'good comment';
|
|
|
|
COMMENT ON TYPE default_test_row IS NULL;
|
2010-10-19 13:21:58 +02:00
|
|
|
COMMENT ON COLUMN default_test_row.nope IS 'bad comment';
|
|
|
|
COMMENT ON COLUMN default_test_row.f1 IS 'good comment';
|
|
|
|
COMMENT ON COLUMN default_test_row.f1 IS NULL;
|
2003-11-21 23:32:49 +01:00
|
|
|
|
2006-02-28 23:37:27 +01:00
|
|
|
-- Check shell type create for existing types
|
|
|
|
CREATE TYPE text_w_default; -- should fail
|
|
|
|
|
2002-08-15 18:36:08 +02:00
|
|
|
DROP TYPE default_test_row CASCADE;
|
|
|
|
|
2001-09-06 04:07:42 +02:00
|
|
|
DROP TABLE default_test;
|
2006-12-30 22:21:56 +01:00
|
|
|
|
2015-04-22 21:23:02 +02:00
|
|
|
-- Check type create with input/output incompatibility
|
|
|
|
CREATE TYPE not_existing_type (INPUT = array_in,
|
|
|
|
OUTPUT = array_out,
|
|
|
|
ELEMENT = int,
|
|
|
|
INTERNALLENGTH = 32);
|
|
|
|
|
2006-12-30 22:21:56 +01:00
|
|
|
-- Check usage of typmod with a user-defined type
|
|
|
|
-- (we have borrowed numeric's typmod functions)
|
|
|
|
|
|
|
|
CREATE TEMP TABLE mytab (foo widget(42,13,7)); -- should fail
|
|
|
|
CREATE TEMP TABLE mytab (foo widget(42,13));
|
|
|
|
|
|
|
|
SELECT format_type(atttypid,atttypmod) FROM pg_attribute
|
|
|
|
WHERE attrelid = 'mytab'::regclass AND attnum > 0;
|