From 311bcfc6b3acdd6fd152798c7f287ddf74fa2a98 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Tue, 16 Apr 2024 21:46:48 +0200 Subject: Adding upstream version 15.4. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/tutorial-populate.html | 59 ++++++++++++++++++++++++++++++++ 1 file changed, 59 insertions(+) create mode 100644 doc/src/sgml/html/tutorial-populate.html (limited to 'doc/src/sgml/html/tutorial-populate.html') diff --git a/doc/src/sgml/html/tutorial-populate.html b/doc/src/sgml/html/tutorial-populate.html new file mode 100644 index 0000000..b214c22 --- /dev/null +++ b/doc/src/sgml/html/tutorial-populate.html @@ -0,0 +1,59 @@ + +2.4. Populating a Table With Rows

2.4. Populating a Table With Rows

+ The INSERT statement is used to populate a table with + rows: + +

+INSERT INTO weather VALUES ('San Francisco', 46, 50, 0.25, '1994-11-27');
+

+ + Note that all data types use rather obvious input formats. + Constants that are not simple numeric values usually must be + surrounded by single quotes ('), as in the example. + The + date type is actually quite flexible in what it + accepts, but for this tutorial we will stick to the unambiguous + format shown here. +

+ The point type requires a coordinate pair as input, + as shown here: +

+INSERT INTO cities VALUES ('San Francisco', '(-194.0, 53.0)');
+

+

+ The syntax used so far requires you to remember the order of the + columns. An alternative syntax allows you to list the columns + explicitly: +

+INSERT INTO weather (city, temp_lo, temp_hi, prcp, date)
+    VALUES ('San Francisco', 43, 57, 0.0, '1994-11-29');
+

+ You can list the columns in a different order if you wish or + even omit some columns, e.g., if the precipitation is unknown: +

+INSERT INTO weather (date, city, temp_hi, temp_lo)
+    VALUES ('1994-11-29', 'Hayward', 54, 37);
+

+ Many developers consider explicitly listing the columns better + style than relying on the order implicitly. +

+ Please enter all the commands shown above so you have some data to + work with in the following sections. +

+ + + You could also have used COPY to load large + amounts of data from flat-text files. This is usually faster + because the COPY command is optimized for this + application while allowing less flexibility than + INSERT. An example would be: + +

+COPY weather FROM '/home/user/weather.txt';
+

+ + where the file name for the source file must be available on the + machine running the backend process, not the client, since the backend process + reads the file directly. You can read more about the + COPY command in COPY. +

\ No newline at end of file -- cgit v1.2.3