File: tutorial-select.html

package info (click to toggle)
postgresql-9.1 9.1.15-0%2Bdeb8u1
  • links: PTS, VCS
  • area: main
  • in suites: jessie-kfreebsd
  • size: 109,092 kB
  • sloc: ansic: 575,877; sql: 43,887; yacc: 26,399; perl: 6,352; lex: 6,171; sh: 5,282; makefile: 3,772; asm: 65; sed: 15; python: 12
file content (452 lines) | stat: -rw-r--r-- 8,033 bytes parent folder | download
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
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>Querying a Table</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
REV="MADE"
HREF="mailto:pgsql-docs@postgresql.org"><LINK
REL="HOME"
TITLE="PostgreSQL 9.1.15 Documentation"
HREF="index.html"><LINK
REL="UP"
TITLE="The SQL Language"
HREF="tutorial-sql.html"><LINK
REL="PREVIOUS"
TITLE="Populating a Table With Rows"
HREF="tutorial-populate.html"><LINK
REL="NEXT"
TITLE="Joins Between Tables"
HREF="tutorial-join.html"><LINK
REL="STYLESHEET"
TYPE="text/css"
HREF="stylesheet.css"><META
HTTP-EQUIV="Content-Type"
CONTENT="text/html; charset=ISO-8859-1"><META
NAME="creation"
CONTENT="2015-02-02T21:03:01"></HEAD
><BODY
CLASS="SECT1"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="5"
ALIGN="center"
VALIGN="bottom"
><A
HREF="index.html"
>PostgreSQL 9.1.15 Documentation</A
></TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="top"
><A
TITLE="Populating a Table With Rows"
HREF="tutorial-populate.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="top"
><A
HREF="tutorial-sql.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="60%"
ALIGN="center"
VALIGN="bottom"
>Chapter 2. The <ACRONYM
CLASS="ACRONYM"
>SQL</ACRONYM
> Language</TD
><TD
WIDTH="20%"
ALIGN="right"
VALIGN="top"
><A
TITLE="Joins Between Tables"
HREF="tutorial-join.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="TUTORIAL-SELECT"
>2.5. Querying a Table</A
></H1
><P
>    
    

    To retrieve data from a table, the table is
    <I
CLASS="FIRSTTERM"
>queried</I
>.  An <ACRONYM
CLASS="ACRONYM"
>SQL</ACRONYM
>
    <TT
CLASS="COMMAND"
>SELECT</TT
> statement is used to do this.  The
    statement is divided into a select list (the part that lists the
    columns to be returned), a table list (the part that lists the
    tables from which to retrieve the data), and an optional
    qualification (the part that specifies any restrictions).  For
    example, to retrieve all the rows of table
    <TT
CLASS="STRUCTNAME"
>weather</TT
>, type:
</P><PRE
CLASS="PROGRAMLISTING"
>SELECT * FROM weather;</PRE
><P>
    Here <TT
CLASS="LITERAL"
>*</TT
> is a shorthand for <SPAN
CLASS="QUOTE"
>"all columns"</SPAN
>.
     <A
NAME="AEN721"
HREF="#FTN.AEN721"
><SPAN
CLASS="footnote"
>[1]</SPAN
></A
>
    So the same result would be had with:
</P><PRE
CLASS="PROGRAMLISTING"
>SELECT city, temp_lo, temp_hi, prcp, date FROM weather;</PRE
><P>

    The output should be:

</P><PRE
CLASS="SCREEN"
>     city      | temp_lo | temp_hi | prcp |    date
---------------+---------+---------+------+------------
 San Francisco |      46 |      50 | 0.25 | 1994-11-27
 San Francisco |      43 |      57 |    0 | 1994-11-29
 Hayward       |      37 |      54 |      | 1994-11-29
(3 rows)</PRE
><P>
   </P
><P
>    You can write expressions, not just simple column references, in the
    select list.  For example, you can do:
</P><PRE
CLASS="PROGRAMLISTING"
>SELECT city, (temp_hi+temp_lo)/2 AS temp_avg, date FROM weather;</PRE
><P>
    This should give:
</P><PRE
CLASS="SCREEN"
>     city      | temp_avg |    date
---------------+----------+------------
 San Francisco |       48 | 1994-11-27
 San Francisco |       50 | 1994-11-29
 Hayward       |       45 | 1994-11-29
(3 rows)</PRE
><P>
    Notice how the <TT
CLASS="LITERAL"
>AS</TT
> clause is used to relabel the
    output column.  (The <TT
CLASS="LITERAL"
>AS</TT
> clause is optional.)
   </P
><P
>    A query can be <SPAN
CLASS="QUOTE"
>"qualified"</SPAN
> by adding a <TT
CLASS="LITERAL"
>WHERE</TT
>
    clause that specifies which rows are wanted.  The <TT
CLASS="LITERAL"
>WHERE</TT
>
    clause contains a Boolean (truth value) expression, and only rows for
    which the Boolean expression is true are returned.  The usual
    Boolean operators (<TT
CLASS="LITERAL"
>AND</TT
>,
    <TT
CLASS="LITERAL"
>OR</TT
>, and <TT
CLASS="LITERAL"
>NOT</TT
>) are allowed in
    the qualification.  For example, the following
    retrieves the weather of San Francisco on rainy days:

</P><PRE
CLASS="PROGRAMLISTING"
>SELECT * FROM weather
    WHERE city = 'San Francisco' AND prcp &gt; 0.0;</PRE
><P>
    Result:
</P><PRE
CLASS="SCREEN"
>     city      | temp_lo | temp_hi | prcp |    date
---------------+---------+---------+------+------------
 San Francisco |      46 |      50 | 0.25 | 1994-11-27
(1 row)</PRE
><P>
   </P
><P
>    

    You can request that the results of a query
    be returned in sorted order:

</P><PRE
CLASS="PROGRAMLISTING"
>SELECT * FROM weather
    ORDER BY city;</PRE
><P>

</P><PRE
CLASS="SCREEN"
>     city      | temp_lo | temp_hi | prcp |    date
---------------+---------+---------+------+------------
 Hayward       |      37 |      54 |      | 1994-11-29
 San Francisco |      43 |      57 |    0 | 1994-11-29
 San Francisco |      46 |      50 | 0.25 | 1994-11-27</PRE
><P>

    In this example, the sort order isn't fully specified, and so you
    might get the San Francisco rows in either order.  But you'd always
    get the results shown above if you do:

</P><PRE
CLASS="PROGRAMLISTING"
>SELECT * FROM weather
    ORDER BY city, temp_lo;</PRE
><P>
   </P
><P
>    
    

    You can request that duplicate rows be removed from the result of
    a query:

</P><PRE
CLASS="PROGRAMLISTING"
>SELECT DISTINCT city
    FROM weather;</PRE
><P>

</P><PRE
CLASS="SCREEN"
>     city
---------------
 Hayward
 San Francisco
(2 rows)</PRE
><P>

    Here again, the result row ordering might vary.
    You can ensure consistent results by using <TT
CLASS="LITERAL"
>DISTINCT</TT
> and
    <TT
CLASS="LITERAL"
>ORDER BY</TT
> together:
     <A
NAME="AEN755"
HREF="#FTN.AEN755"
><SPAN
CLASS="footnote"
>[2]</SPAN
></A
>

</P><PRE
CLASS="PROGRAMLISTING"
>SELECT DISTINCT city
    FROM weather
    ORDER BY city;</PRE
><P>
   </P
></DIV
><H3
CLASS="FOOTNOTES"
>Notes</H3
><TABLE
BORDER="0"
CLASS="FOOTNOTES"
WIDTH="100%"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="5%"
><A
NAME="FTN.AEN721"
HREF="tutorial-select.html#AEN721"
><SPAN
CLASS="footnote"
>[1]</SPAN
></A
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="95%"
><P
>       While <TT
CLASS="LITERAL"
>SELECT *</TT
> is useful for off-the-cuff
       queries, it is widely considered bad style in production code,
       since adding a column to the table would change the results.
      </P
></TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="5%"
><A
NAME="FTN.AEN755"
HREF="tutorial-select.html#AEN755"
><SPAN
CLASS="footnote"
>[2]</SPAN
></A
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="95%"
><P
>       In some database systems, including older versions of
       <SPAN
CLASS="PRODUCTNAME"
>PostgreSQL</SPAN
>, the implementation of
       <TT
CLASS="LITERAL"
>DISTINCT</TT
> automatically orders the rows and
       so <TT
CLASS="LITERAL"
>ORDER BY</TT
> is unnecessary.  But this is not
       required by the SQL standard, and current
       <SPAN
CLASS="PRODUCTNAME"
>PostgreSQL</SPAN
> does not guarantee that
       <TT
CLASS="LITERAL"
>DISTINCT</TT
> causes the rows to be ordered.
      </P
></TD
></TR
></TABLE
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="tutorial-populate.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="tutorial-join.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Populating a Table With Rows</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="tutorial-sql.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Joins Between Tables</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>