summaryrefslogtreecommitdiff
path: root/src/test/regress/expected/char_2.out
blob: ebde0f3e59fb95adb662f73ce190e8164937ee57 (plain)
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
--
-- CHAR
--
-- Per SQL standard, CHAR means character(1), that is a varlena type
-- with a constraint restricting it to one character (not byte)
SELECT char 'c' = char 'c' AS true;
 true 
------
 t
(1 row)

--
-- Build a table for testing
-- (This temporarily hides the table created in test_setup.sql)
--
CREATE TEMP TABLE CHAR_TBL(f1 char);
INSERT INTO CHAR_TBL (f1) VALUES ('a');
INSERT INTO CHAR_TBL (f1) VALUES ('A');
-- any of the following three input formats are acceptable
INSERT INTO CHAR_TBL (f1) VALUES ('1');
INSERT INTO CHAR_TBL (f1) VALUES (2);
INSERT INTO CHAR_TBL (f1) VALUES ('3');
-- zero-length char
INSERT INTO CHAR_TBL (f1) VALUES ('');
-- try char's of greater than 1 length
INSERT INTO CHAR_TBL (f1) VALUES ('cd');
ERROR:  value too long for type character(1)
INSERT INTO CHAR_TBL (f1) VALUES ('c     ');
SELECT * FROM CHAR_TBL;
 f1 
----
 a
 A
 1
 2
 3
  
 c
(7 rows)

SELECT c.*
   FROM CHAR_TBL c
   WHERE c.f1 <> 'a';
 f1 
----
 A
 1
 2
 3
  
 c
(6 rows)

SELECT c.*
   FROM CHAR_TBL c
   WHERE c.f1 = 'a';
 f1 
----
 a
(1 row)

SELECT c.*
   FROM CHAR_TBL c
   WHERE c.f1 < 'a';
 f1 
----
  
(1 row)

SELECT c.*
   FROM CHAR_TBL c
   WHERE c.f1 <= 'a';
 f1 
----
 a
  
(2 rows)

SELECT c.*
   FROM CHAR_TBL c
   WHERE c.f1 > 'a';
 f1 
----
 A
 1
 2
 3
 c
(5 rows)

SELECT c.*
   FROM CHAR_TBL c
   WHERE c.f1 >= 'a';
 f1 
----
 a
 A
 1
 2
 3
 c
(6 rows)

DROP TABLE CHAR_TBL;
--
-- Now test longer arrays of char
--
-- This char_tbl was already created and filled in test_setup.sql.
-- Here we just try to insert bad values.
--
INSERT INTO CHAR_TBL (f1) VALUES ('abcde');
ERROR:  value too long for type character(4)
SELECT * FROM CHAR_TBL;
  f1  
------
 a   
 ab  
 abcd
 abcd
(4 rows)

-- Also try it with non-error-throwing API
SELECT pg_input_is_valid('abcd  ', 'char(4)');
 pg_input_is_valid 
-------------------
 t
(1 row)

SELECT pg_input_is_valid('abcde', 'char(4)');
 pg_input_is_valid 
-------------------
 f
(1 row)

SELECT * FROM pg_input_error_info('abcde', 'char(4)');
               message                | detail | hint | sql_error_code 
--------------------------------------+--------+------+----------------
 value too long for type character(4) |        |      | 22001
(1 row)

--
-- Also test "char", which is an ad-hoc one-byte type.  It can only
-- really store ASCII characters, but we allow high-bit-set characters
-- to be accessed via bytea-like escapes.
--
SELECT 'a'::"char";
 char 
------
 a
(1 row)

SELECT '\101'::"char";
 char 
------
 A
(1 row)

SELECT '\377'::"char";
 char 
------
 \377
(1 row)

SELECT 'a'::"char"::text;
 text 
------
 a
(1 row)

SELECT '\377'::"char"::text;
 text 
------
 \377
(1 row)

SELECT '\000'::"char"::text;
 text 
------
 
(1 row)

SELECT 'a'::text::"char";
 char 
------
 a
(1 row)

SELECT '\377'::text::"char";
 char 
------
 \377
(1 row)

SELECT ''::text::"char";
 char 
------
 
(1 row)