Database Systems Design Implementation and Management 11th Edition Coronel Solutions Manual

Database Systems Design Implementation and
Management 11th Edition Coronel Solutions Manual
download
https://testbankfan.com/product/database-systems-design-
implementation-and-management-11th-edition-coronel-solutions-
manual/
Find test banks or solution manuals at testbankfan.com today!

Here are some recommended products for you. Click the link to
download, or explore more at testbankfan.com
Database Systems Design Implementation and Management 11th
Edition Coronel Test Bank
implementation-and-management-11th-edition-coronel-test-bank/
Database Systems Design Implementation and Management 12th
Edition Coronel Solutions Manual
implementation-and-management-12th-edition-coronel-solutions-manual/
Database Systems Design Implementation And Management 13th
Edition Coronel Solutions Manual
implementation-and-management-13th-edition-coronel-solutions-manual/
Business Law in Canada Canadian Edition Canadian 10th
Edition Yates Test Bank
https://testbankfan.com/product/business-law-in-canada-canadian-
edition-canadian-10th-edition-yates-test-bank/

Modern Advanced Accounting in Canada Canadian 7th Edition
Hilton Solutions Manual
https://testbankfan.com/product/modern-advanced-accounting-in-canada-
canadian-7th-edition-hilton-solutions-manual/
Information Systems A Managers Guide to Harnessing
Technology 1st Edition Gallaugher Test Bank
https://testbankfan.com/product/information-systems-a-managers-guide-
to-harnessing-technology-1st-edition-gallaugher-test-bank/
Organizations Behavior Structure Processes 14th Edition
Gibson Test Bank
https://testbankfan.com/product/organizations-behavior-structure-
processes-14th-edition-gibson-test-bank/
Finite Mathematics and Its Applications 12th Edition
Goldstein Solutions Manual
https://testbankfan.com/product/finite-mathematics-and-its-
applications-12th-edition-goldstein-solutions-manual/
Human Resource Information Systems 3rd Edition Kavanagh
Test Bank
https://testbankfan.com/product/human-resource-information-
systems-3rd-edition-kavanagh-test-bank/

Chemistry An Atoms First Approach 2nd Edition Zumdahl
Solutions Manual
https://testbankfan.com/product/chemistry-an-atoms-first-approach-2nd-
edition-zumdahl-solutions-manual/

Chapter 7 An Introduction to Structured Query Language (SQL)
239
Chapter 7
Introduction to Structured Query Language (SQL)
NOTE
Several points are worth emphasizing:
• We have provided the SQL scripts for both chapters 7 and 8. These scripts are intended to
facilitate the flow of the material presented to the class. However, given the comments made
by our students, the scripts should not replace the manual typing of the SQL commands by
students. Some students learn SQL better when they have a chance to type their own
commands and get the feedback provided by their errors. We recommend that the students use
their lab time to practice the commands manually.
• Because this chapter focuses on learning SQL, we recommend that you use the Microsoft
Access SQL window to type SQL queries. Using this approach, you will be able to
demonstrate the interoperability of standard SQL. For example, you can cut and paste the same
SQL command from the SQL query window in Microsoft Access, to Oracle SQL * Plus and to
MS SQL Query Analyzer. This approach achieves two objectives:
➢ It demonstrates that adhering to the SQL standard means that most of the SQL code
will be portable among DBMSes.
➢ It also demonstrates that even a widely accepted SQL standard is sometimes
implemented with slight distinctions by different vendors. For example, the treatment
of date formats in Microsoft Access and Oracle is slightly different.
Answers to Review Questions
1. In a SELECT query, what is the difference between a WHERE clause and a HAVING clause?
Both a WHERE clause and a HAVING clause can be used to eliminate rows from the results of a
query. The differences are 1) the WHERE clause eliminates rows before any grouping for aggregate
functions occurs while the HAVING clause eliminates groups after the grouping has been done, and
2) the WHERE clause cannot contain an aggregate function but the HAVING clause can.
2. Explain why the following command would create an error, and what changes could be made
to fix the error.
SELECT V_CODE, SUM(P_QOH) FROM PRODUCT;
The command would generate an error because an aggregate function is applied to the P_QOH
attribute but V_CODE is neither in an aggregate function or in a GROUP BY. This can be fixed by
either 1) placing V_CODE in an appropriate aggregate function based on the data that is being
requested by the user, 2) adding a GROUP BY clause to group by values of V_CODE (i.e. GROUP
BY V_CODE), 3) removing the V_CODE attribute from the SELECT clause, or 4) removing the
Sum aggregate function from P_QOH. Which of these solutions is most appropriate depends on the
question that the query was intended to answer.

240
3. What type of integrity is enforced when a primary key is declared?
Creating a primary key constraint enforces entity integrity (i.e. no part of the primary key can
contain a null and the primary key values must be unique).
4. Explain why it might be more appropriate to declare an attribute that contains only digits as a
character data type instead of a numeric data type.
An attribute that contains only digits may be properly defined as character data when the values are
nominal; that is, the values do not have numerical significance but serve only as labels such as ZIP
codes and telephone numbers. One easy test is to consider whether or not a leading zero should be
retained. For the ZIP code 03133, the leading zero should be retained; therefore, it is appropriate to
define it as character data. For the quantity on hand of 120, we would not expect to retain a leading
zero such as 0120; therefore, it is appropriate to define the quantity on hand as a numeric data type.
5. What is the difference between a column constraint and a table constraint?
A column constraint can refer to only the attribute with which it is specified. A table constraint can
refer to any attributes in the table.
6. What are “referential constraint actions”?
Referential constraint actions, such as ON DELETE CASCADE, are default actions that the DBMS
should take when a DML command would result in a referential integrity constraint violation.
Without referential constraint actions, DML commands that would result in a violation of referential
integrity will fail with an error indicating that the referential integrity constrain cannot be violated.
Referential constraint actions can allow the DML command to successfully complete while making
the designated changes to the related records to maintain referential integrity.
7. Rewrite the following WHERE clause without the use of the IN special operator.
WHERE V_STATE IN (‘TN’, ‘FL’, ‘GA’)
WHERE V_STATE = 'TN' OR V_STATE = 'FL' OR V_STATE = 'GA'
Notice that each criteria must be complete (i.e. attribute-operator-value).
8. Explain the difference between an ORDER BY clause and a GROUP BY clause.
An ORDER BY clause has no impact on which rows are returned by the query, it simply sorts those
rows into the specified order. A GROUP BY clause does impact the rows that are returned by the
query. A GROUP BY clause gathers rows into collections that can be acted on by aggregate
functions.
9. Explain why the two following commands produce different results.
SELECT DISTINCT COUNT (V_CODE) FROM PRODUCT;

241
SELECT COUNT (DISTINCT V_CODE) FROM PRODUCT;
The difference is in the order of operations. The first command executes the Count function to count
the number of values in V_CODE (say the count returns "14" for example) including duplicate
values, and then the Distinct keyword only allows one count of that value to be displayed (only one
row with the value "14" appears as the result). The second command applies the Distinct keyword to
the V_CODEs before the count is taken so only unique values are counted.
10. What is the difference between the COUNT aggregate function and the SUM aggregate
function?
COUNT returns the number of values without regard to what the values are. SUM adds the values
together and can only be applied to numeric values.
11. Explain why it would be preferable to use a DATE data type to store date data instead of a
character data type.
The DATE data type uses numeric values based on the Julian calendar to store dates. This makes
date arithmetic such as adding and subtracting days or fractions of days possible (as well as
numerous special date-oriented functions discussed in the next chapter!).
12. What is a recursive join?
A recursive join is a join in which a table is joined to itself.
Problem Solutions
O n l i n e C o n t e n t
Problems 1 – 25 are based on the Ch07_ConstructCo database located www.cengagebrain.com. This database
is stored in Microsoft Access format. The website provides Oracle, MySQL, and MS SQL Server script files.
The Ch07_ConstructCo database stores data for a consulting company that tracks all charges to
projects. The charges are based on the hours each employee works on each project. The structure and
contents of the Ch07_ConstructCo database are shown in Figure P7.1.
Figure P7.1 Structure and contents of the Ch07_ConstructCo database

242
Note that the ASSIGNMENT table in Figure P7.1 stores the JOB_CHG_HOUR values as an
attribute (ASSIGN_CHG_HR) to maintain historical accuracy of the data. The
JOB_CHG_HOUR values are likely to change over time. In fact, a JOB_CHG_HOUR change will
be reflected in the ASSIGNMENT table. And, naturally, the employee primary job assignment
might change, so the ASSIGN_JOB is also stored. Because those attributes are required to
maintain the historical accuracy of the data, they are not redundant.
Given the structure and contents of the Ch07_ConstructCo database shown in Figure P7.1, use
SQL commands to answer Problems 1–25.
1. Write the SQL code that will create the table structure for a table named EMP_1. This table is
a subset of the EMPLOYEE table. The basic EMP_1 table structure is summarized in the table
below. (Note that the JOB_CODE is the FK to JOB.)

243
ATTRIBUTE (FIELD) NAME DATA DECLARATION
EMP_NUM CHAR(3)
EMP_LNAME VARCHAR(15)
EMP_FNAME VARCHAR(15)
EMP_INITIAL CHAR(1)
EMP_HIREDATE DATE
JOB_CODE CHAR(3)
CREATE TABLE EMP_1 (
EMP_NUM CHAR(3) PRIMARY KEY,
EMP_LNAME VARCHAR(15) NOT NULL,
EMP_FNAME VARCHAR(15) NOT NULL,
EMP_INITIAL CHAR(1),
EMP_HIREDATE DATE,
JOB_CODE CHAR(3),
FOREIGN KEY (JOB_CODE) REFERENCES JOB);
NOTE
We have already provided the EMP_1 table for you. If you try to run the preceding query,
you will get an error message because the EMP_1 table already exits.
2. Having created the table structure in Problem 1, write the SQL code to enter the first two rows
for the table shown in Figure P7.2.
Figure P7.2 The contents of the EMP_1 table
INSERT INTO EMP_1 VALUES (‘101’, ‘News’, ‘John’, ‘G’, ’08-Nov-00’, ‘502’);
INSERT INTO EMP_1 VALUES (‘102’, ‘Senior’, ‘David’, ‘H’, ’12-Jul-89’, ‘501’);
3. Assuming the data shown in the EMP_1 table have been entered, write the SQL code that will
list all attributes for a job code of 502.
SELECT *
FROM EMP_1
WHERE JOB_CODE = ‘502’;

244
4. Write the SQL code that will save the changes made to the EMP_1 table.
COMMIT;
5. Write the SQL code to change the job code to 501 for the person whose employee number
(EMP_NUM) is 107. After you have completed the task, examine the results, and then reset the
job code to its original value.
UPDATE EMP_1
SET JOB_CODE = ‘501’
WHERE EMP_NUM = ‘107’;
To see the changes:
SELECT *
FROM EMP_1
To reset, use
ROLLBACK;
6. Write the SQL code to delete the row for the person named William Smithfield, who was hired
on June 22, 2004, and whose job code classification is 500. (Hint: Use logical operators to
include all of the information given in this problem.)
DELETE FROM EMP_1
WHERE EMP_LNAME = 'Smithfield'
AND EMP_FNAME = 'William'
AND EMP_HIREDATE = '22-June-04'
AND JOB_CODE = '500';
7. Write the SQL code that will restore the data to its original status; that is, the table should
contain the data that existed before you made the changes in Problems 5 and 6.
ROLLBACK;

245
8. Write the SQL code to create a copy of EMP_1, naming the copy EMP_2. Then write the SQL
code that will add the attributes EMP_PCT and PROJ_NUM to its structure. The EMP_PCT
is the bonus percentage to be paid to each employee. The new attribute characteristics are:
EMP_PCTNUMBER(4,2)
PROJ_NUMCHAR(3)
(Note: If your SQL implementation allows it, you may use DECIMAL(4,2) rather than
NUMBER(4,2).)
There are two way to get this job done. The two possible solutions are shown next.
Solution A:
CREATE TABLE EMP_2 (
EMP_NUM CHAR(3) NOT NULL UNIQUE,
EMP_LNAME VARCHAR(15) NOT NULL,
EMP_FNAME VARCHAR(15) NOT NULL,
EMP_INITIAL CHAR(1),
EMP_HIREDATE DATE NOT NULL,
JOB_CODE CHAR(3) NOT NULL,
PRIMARY KEY (EMP_NUM),
FOREIGN KEY (JOB_CODE) REFERENCES JOB);
INSERT INTO EMP_2 SELECT * FROM EMP_1;
ALTER TABLE EMP_2
ADD (EMP_PCT NUMBER (4,2)),
ADD (PROJ_NUM CHAR(3));
Solution B:
CREATE TABLE EMP_2 AS SELECT * FROM EMP_1;
ALTER TABLE EMP_2
ADD (EMP_PCT NUMBER (4,2)),
ADD (PROJ_NUM CHAR(3));
9. Write the SQL code to change the EMP_PCT value to 3.85 for the person whose employee
number (EMP_NUM) is 103. Next, write the SQL command sequences to change the
EMP_PCT values as shown in Figure P7.9.

246
Figure P7.9 The contents of the EMP_2 table
UPDATE EMP_2
SET EMP_PCT = 3.85
WHERE EMP_NUM = '103';
To enter the remaining EMP_PCT values, use the following SQL statements:
UPDATEEMP_2
SET EMP_PCT = 5.00
UPDATEEMP_2
SET EMP_PCT = 8.00
Follow this format for the remaining rows.
10. Using a single command sequence, write the SQL code that will change the project number
(PROJ_NUM) to 18 for all employees whose job classification (JOB_CODE) is 500.
UPDATE EMP_2
SET PROJ_NUM = '18'
WHERE JOB_CODE = '500';
11. Using a single command sequence, write the SQL code that will change the project number
(PROJ_NUM) to 25 for all employees whose job classification (JOB_CODE) is 502 or higher.
When you finish Problems 10 and 11, the EMP_2 table will contain the data shown in Figure
P7.11. (You may assume that the table has been saved again at this point.)

247
Figure P7.11 The EMP_2 table contents after the modification
UPDATE EMP_2
SET PROJ_NUM = '25'
WHERE JOB_CODE > = '502'
12. Write the SQL code that will change the PROJ_NUM to 14 for those employees who were
hired before January 1, 1994 and whose job code is at least 501. (You may assume that the
table will be restored to its condition preceding this question.)
UPDATE EMP_2
SET PROJ_NUM = '14'
WHERE EMP_HIREDATE <= ' 01-Jan-94'
AND JOB_CODE >= '501';
13. Write the two SQL command sequences required to:
There are many ways to accomplish both tasks. We are illustrating the shortest way to do the job
next.
a. Create a temporary table named TEMP_1 whose structure is composed of the EMP_2
attributes EMP_NUM and EMP_PCT.
The SQL code shown in problem 13b contains the solution for problem 13a.
b. Copy the matching EMP_2 values into the TEMP_1 table.
CREATE TABLE TEMP_1 AS SELECT EMP_NUM, EMP_PCT FROM EMP_2;
An alternate way would be to create the table and then, use an INSERT with a sub-select to
populate the rows.
CREATE TABLE TEMP_1 AS (
EMP_NUM CHAR(3),
EMP_PCT NUMBER(4,2));
INSERT INTO TEMP_1
SELECT EMP_NUM, EMP_PCT FROM EMP_2;

248
14. Write the SQL command that will delete the newly created TEMP_1 table from the database.
DROP TABLE TEMP_1;
15. Write the SQL code required to list all employees whose last names start with Smith. In other
words, the rows for both Smith and Smithfield should be included in the listing. Assume case
sensitivity.
SELECT *
FROM EMP_2
WHERE EMP_LNAME LIKE 'Smith%';
16. Using the EMPLOYEE, JOB, and PROJECT tables in the Ch07_ConstructCo database (see
Figure P7.1), write the SQL code that will produce the results shown in Figure P7.16.
Figure P7.16 The query results for Problem 16
SELECT PROJ_NAME, PROJ_VALUE, PROJ_BALANCE, EMPLOYEE.EMP_LNAME,
EMP_FNAME, EMP_INITIAL, EMPLOYEE.JOB_CODE, JOB.JOB_DESCRIPTION,
JOB.JOB_CHG_HOUR
FROM PROJECT, EMPLOYEE, JOB
WHERE EMPLOYEE.EMP_NUM = PROJECT.EMP_NUM
AND JOB.JOB_CODE = EMPLOYEE.JOB_CODE;
17. Write the SQL code that will produce a virtual table named REP_1. The virtual table should
contain the same information that was shown in Problem 16.
CREATE VIEW REP_1 AS
SELECT PROJ_NAME, PROJ_VALUE, PROJ_BALANCE, EMPLOYEE.EMP_LNAME,
EMP_FNAME, EMP_INITIAL, EMPLOYEE.JOB_CODE, JOB.JOB_DESCRIPTION,
JOB.JOB_CHG_HOUR
FROM PROJECT, EMPLOYEE, JOB
WHERE EMPLOYEE.EMP_NUM = PROJECT.EMP_NUM
AND JOB.JOB_CODE = EMPLOYEE.JOB_CODE;

249
18. Write the SQL code to find the average bonus percentage in the EMP_2 table you created in
Problem 8.
SELECT AVG(EMP_PCT)
FROM EMP_2;
19. Write the SQL code that will produce a listing for the data in the EMP_2 table in ascending
order by the bonus percentage.
SELECT *
FROM EMP_2
ORDER BY EMP_PCT;
20. Write the SQL code that will list only the distinct project numbers found in the EMP_2 table.
SELECT DISTINTC PROJ_NUM
FROM EMP_2;
21. Write the SQL code to calculate the ASSIGN_CHARGE values in the ASSIGNMENT table in
the Ch07_ConstructCo database. (See Figure P7.1.) Note that ASSIGN_CHARGE is a derived
attribute that is calculated by multiplying ASSIGN_CHG_HR by ASSIGN_HOURS.
UPDATE ASSIGNMENT
SET ASSIGN_CHARGE = ASSIGN_CHG_HR * ASSIGN_HOURS;
22. Using the data in the ASSIGNMENT table, write the SQL code that will yield the total number
of hours worked for each employee and the total charges stemming from those hours worked.
The results of running that query are shown in Figure P7.22.
Figure P7.22 Total hours and charges by employee

250
SELECT ASSIGNMENT.EMP_NUM, EMPLOYEE.EMP_LNAME,
Sum(ASSIGNMENT.ASSIGN_HOURS) AS SumOfASSIGN_HOURS,
Sum(ASSIGNMENT.ASSIGN_CHARGE) AS SumOfASSIGN_CHARGE
FROM EMPLOYEE, ASSIGNMENT
WHERE EMPLOYEE.EMP_NUM = ASSIGNMENT.EMP_NUM
GROUP BY ASSIGNMENT.EMP_NUM, EMPLOYEE.EMP_LNAME;
23. Write a query to produce the total number of hours and charges for each of the projects
represented in the ASSIGNMENT table. The output is shown in Figure P7.23.
Figure P7.23 Total hour and charges by project
SELECT ASSIGNMENT.PROJ_NUM,
Sum(ASSIGNMENT.ASSIGN_CHARGE) AS SumOfASSIGN_CHARGE
FROM ASSIGNMENT
GROUP BY ASSIGNMENT.PROJ_NUM
24. Write the SQL code to generate the total hours worked and the total charges made by all
employees. The results are shown in Figure P7.24. (Hint: This is a nested query. If you use
Microsoft Access, you can generate the result by using the query output shown in Figure P7.22
as the basis for the query that will produce the output shown in Figure P7.24.)
Figure P7.24 Total hours and charges, all employees
Solution A:
SELECT Sum(SumOfASSIGN_HOURS) AS SumOfASSIGN_HOURS,
Sum(SumOfASSIGN_CHARGE) AS SumOfASSIGN_CHARGE
FROM Q23;
or

251
Sum(SumOfASSIGN_CHARGE as SumOfASSIGN_CHARGE
FROM (SELECT ASSIGNMENT.PROJ_NUM,
Sum(ASSIGNMENT.ASSIGN_CHARGE) AS
SumOfASSIGN_CHARGE
FROM ASSIGNMENT
);
Solution B:
FROM Q22;
or
FROM (SELECT ASSIGNMENT.EMP_NUM, EMPLOYEE.EMP_LNAME,
SumOfASSIGN_CHARGE
FROM EMPLOYEE, ASSIGNMENT
WHERE EMPLOYEE.EMP_NUM = ASSIGNMENT.EMP_NUM
GROUP BY ASSIGNMENT.EMP_NUM, EMPLOYEE.EMP_LNAME
);

252
25. Write the SQL code to generate the total hours worked and the total charges made to all
projects. The results should be the same as those shown in Figure P7.24. (Hint: This is a nested
query. If you use Microsoft Access, you can generate the result by using the query output
shown in Figure P7.23 as the basis for this query.)
FROM Q23;
or
Sum(SumOfASSIGN_CHARGE as SumOfASSIGN_CHARGE
FROM (SELECT ASSIGNMENT.PROJ_NUM,
SumOfASSIGN_CHARGE
FROM ASSIGNMENT
);
O n l i n e C o n t e n t
Problems 26−43 are based on the Ch07_SaleCo database, which is available at www.cengagebrain.com.
This database is stored in Microsoft Access format. Oracle, MySQL and MS SQL Server script files are
available at www.cengagebrain.com.
The structure and contents of the Ch07_SaleCo database are shown in Figure P7.26. Use this
database to answer the following problems. Save each query as QXX, where XX is the problem
number.
26. Write a query to count the number of invoices.
SELECT COUNT(*) FROM INVOICE;
27. Write a query to count the number of customers with a customer balance over $500.
SELECT COUNT(*)
FROM CUSTOMER
WHERE CUS_BALANCE >500;

253
28. Generate a listing of all purchases made by the customers, using the output shown in Figure
P7.28 as your guide. (Hint: Use the ORDER BY clause to order the resulting rows as shown in
Figure P7.28)
FIGURE P7.28 List of Customer Purchases
SELECT INVOICE.CUS_CODE, INVOICE.INV_NUMBER, INVOICE.INV_DATE,
PRODUCT.P_DESCRIPT, LINE.LINE_UNITS, LINE.LINE_PRICE
FROM CUSTOMER, INVOICE, LINE, PRODUCT
WHERE CUSTOMER.CUS_CODE = INVOICE.CUS_CODE
AND INVOICE.INV_NUMBER = LINE.INV_NUMBER
AND PRODUCT.P_CODE = LINE.P_CODE
ORDER BY INVOICE.CUS_CODE, INVOICE.INV_NUMBER, PRODUCT.P_DESCRIPT;

Random documents with unrelated
content Scribd suggests to you:

LXXVII
L’ouvrier et sa femme, venus de l’ouest, creusent la terre pour faire des
briques et construire le four.
Leur petite fille va au bord de la rivière, où elle n’en finit pas de nettoyer
les pots et les casseroles.
Le petit frère, tout brun et tondu, nu et couvert de boue, la suit et, assis
sur la berge, attend patiemment qu’elle l’appelle.
La fillette s’en retourne à la maison, sa cruche pleine d’eau sur la tête, un
pot de cuivre tout reluisant dans la main gauche et tenant l’enfant de l’autre
main. Elle est la mignonne servante de sa mère et déjà sérieuse sous le
poids des soucis domestiques.
Un jour je vis le petit garçon tout nu étendu sur l’herbe. Dans l’eau sa
sœur était assise, frottant un pot à boire avec une poignée de sable, le
tournant et le retournant.
Tout près de là un agneau à la douce toison broutait le long de la berge.
Il s’approcha de l’enfant et, soudain, bêla avec force.
L’enfant tressaillit et se mit à crier.
La sœur laissa là son nettoyage et accourut.
Elle entoura son frère d’un bras, l’agneau de l’autre et, leur partageant ses
caresses, elle unit, dans le même lien de tendresse, l’enfant de l’homme et
le petit de la bête.

LXXVIII
C’était au mois de Mai. La chaleur suffocante du milieu du jour semblait
interminable. La terre desséchée baillait de soif.
J’entendis une voix appeler de l’autre côté de la rivière: «Viens, mon
bien-aimé.»
Je fermai mon livre et j’ouvris la fenêtre. Je vis un gros buffle, aux flancs
tachés de boue, qui se tenait au bord de la rivière et qui me regardait de ses
yeux placides et patients. Un garçonnet, dans l’eau jusqu’à mi-jambes,
l’appelait pour prendre son bain.
Je souris, amusé, et je sentis une douceur effleurer mon cœur.

LXXIX
Souvent je me demande jusqu’à quel point peuvent se reconnaître
l’homme et la bête qui ne parle pas.
A travers quel paradis primitif, au matin de la lointaine création, courut le
sentier où leurs cœurs se rencontrèrent.
Bien que leur parenté ait été longtemps oubliée, les traces de leur
constante union ne se sont pas effacées.
Et soudain, dans une harmonie sans paroles, un souvenir confus s’éveille
et la bête regarde le visage de l’homme avec une tendre confiance et
l’homme abaisse ses yeux vers la bête avec une tendresse amusée.
Il semble que les deux amis se rencontrent masqués et se reconnaissent
vaguement sous le déguisement.

LXXX
D’un regard de vos yeux, belle femme, vous pourriez piller le trésor des
chants jaillis de la harpe des poëtes.
Mais vous n’avez pas d’oreille pour leurs louanges; c’est pourquoi je
viens vous louer.
Vous pourriez tenir humiliées à vos pieds les têtes les plus fières du
monde.
Mais, parmi vos adorateurs, les ignorés de la gloire sont vos préférés;
c’est pourquoi je vous adore.
La perfection de vos bras ajouterait à la splendeur royale, si vous y
touchiez.
Mais vous les employez à épousseter et à tenir propre votre humble
demeure; c’est pourquoi je suis rempli de respect pour vous.

LXXXI
Mort, ô ma Mort, pourquoi chuchotes-tu si bas à mes oreilles?
Quand, vers le soir, les fleurs se flétrissent et que le bétail revient à
l’étable, sournoisement tu viens, à mes côtés, prononcer des paroles que je
ne comprends pas.
Espères-tu ainsi, me courtiser et me conquérir? m’endormir, dans un
murmure, sous l’opium de tes froids baisers? Mort, ô ma Mort!
N’y aura-t-il pas, pour nos noces, quelque somptueuse cérémonie?
N’attacheras-tu pas d’une guirlande de fleurs les torsades de tes boucles
fauves?
N’y a-t-il personne pour porter devant toi ta bannière et la nuit ne sera-t-
elle pas enflammée de tes torches rouges, Mort, ô ma Mort?
Viens au claquement de tes cymbales de coquillages, viens dans une nuit
sans sommeil.
Revêts-moi du manteau écarlate; étreins ma main et prends-moi.
Que ton char soit tout prêt à ma porte et que tes chevaux hennissent
d’impatience.
Lève le voile et, fièrement, regarde-moi en plein visage, Mort, ô ma
Mort!

LXXXII
Ce soir, ma jeune épouse et moi, nous allons jouer le jeu de la mort.
La nuit est noire, les nuages, dans le ciel, sont fantasques et les vagues de
la mer sont en délire.
Nous avons quitté notre couche de songes; nous avons ouvert la porte
toute grande et nous sommes sortis, ma jeune épouse et moi.
Nous nous sommes assis sur l’escarpolette et le vent d’orage nous a
brutalement poussés par derrière.
Ma jeune épouse s’est dressée brusquement; épouvantée et charmée à la
fois, elle tremble et se cramponne à mon sein.
Longtemps, je lui avais tendrement fait la cour.
J’avais fait pour elle un lit de fleurs; je fermais les portes pour que la
lumière trop vive n’offusque pas ses yeux.
Je la baisais doucement sur les lèvres et lui murmurais à l’oreille de
douces paroles; elle défaillait presque de langueur.
Elle était comme perdue dans le brouillard d’une immense et vague
douceur.
Elle ne répondait pas à la pression de mes mains; mes chants ne
pouvaient plus l’éveiller.
Ce soir, nous est venu l’appel de l’orage, l’appel des sauvages éléments.
Ma petite épouse a frissonné; elle s’est levée et m’a entraîné par la main.
Sa chevelure flotte; son voile bat dans le vent, sa guirlande frémit sur sa
poitrine.
La poussée de la mort l’a rejetée dans la vie.
Nous voilà face à face et cœur à cœur, mon épouse et moi.

LXXXIII
Elle demeurait au flanc de la colline, au bord d’un champ de maïs, près
de la source qui s’épanche en riants ruisseaux, à travers l’ombre solennelle
des vieux arbres. Les femmes venaient là pour remplir leurs cruches; là les
voyageurs aimaient à s’asseoir et à causer. Là, chaque jour, elle travaillait et
rêvait, au bruit du courant bouillonnant.
Un soir, un étranger descendit d’un pic perdu dans les nuages; les boucles
de ses cheveux étaient emmêlées comme de lourds serpents. Etonnés, nous
lui demandâmes: «qui es-tu»? Sans répondre, il s’assit près du ruisseau
jaseur et, silencieusement regarda la hutte où elle demeurait. Nous eûmes
peur et nous revînmes de nuit à la maison.
Le lendemain matin, quand les femmes vinrent chercher de l’eau à la
source, près des grands «Deodora», elles trouvèrent ouvertes les portes de
sa hutte, mais sa voix ne s’y faisait plus entendre... et où était son souriant
visage?... La cruche vide gisait sur le plancher et, dans un coin, la lampe
s’était consumée. Personne ne sut où elle s’était enfuie avant l’aube.—
L’étranger aussi avait disparu.
Au mois de mai, le soleil devint ardent et la neige se fondit; nous nous
assîmes près de la source et nous pleurâmes. Nous nous demandions: Y a-t-
il, dans le pays où elle est allée, une source où elle puisse trouver l’eau en
ces jours chauds et altérés? Et nous pensions avec effroi: Y a-t-il même un
pays au delà de ces collines où nous vivons?
C’était une nuit d’été; la brise du sud soufflait et j’étais assis dans sa
chambre abandonnée, où était demeurée la lampe éteinte, quand, soudain,
devant mes yeux, les collines s’écartèrent comme des rideaux qu’on aurait
tirés: «Ah! c’est elle qui vient. Comment vas-tu, mon enfant? Es-tu
heureuse? Mais où peux-tu t’abriter sous ce ciel découvert? Hélas! notre
source n’est pas là pour apaiser ta soif!»
«C’est ici le même ciel, dit-elle, libre seulement de la barrière des
collines—ceci est le même ruisseau grandi en une rivière,—c’est la même
terre élargie en une plaine». «Il y a tout, là, soupirai-je, seulement nous n’y
sommes pas». Elle sourit tristement et dit: «Vous êtes dans mon cœur». Je

m’éveillai et entendis le babil du ruisseau et le frémissement des «deodora»
dans la nuit.

LXXXIV
Sur les champs de riz verts et jaunes, les ombres des nuages d’automne
glissent bientôt chassés par le rapide soleil.
Les abeilles oublient de sucer le miel des fleurs; ivres de lumière, elles
voltigent follement et bourdonnent.
Les canards, dans les îles de la rivière, crient de joie sans savoir pourquoi.
Amis, que personne, ce matin, ne rentre à la maison; que personne n’aille
au travail.
Prenons d’assaut le ciel bleu; emparons-nous de l’espace comme d’un
butin au gré de notre course.
Le rire flotte dans l’air, comme l’écume sur l’eau.
Amis, gaspillons notre matinée en chansons futiles.

LXXXV
Qui es-tu, lecteur, toi qui, dans cent ans, liras mes vers?
Je ne puis t’envoyer une seule fleur de cette couronne printanière, ni un
seul rayon d’or de ce lointain nuage.
Ouvre tes portes et regarde au loin.
Dans ton jardin en fleurs, cueille les souvenirs parfumés des fleurs fanées
d’il y a cent ans.
Puisses-tu sentir, dans la joie de ton cœur, la joie vivante qui, un matin de
printemps, chanta, lançant sa voix joyeuse par delà cent années.
ACHEVÉ D’IMPRIMER, LE
TRENTE JUIN MIL NEUF
CENT VINGT, PAR L’IMPRI-
MERIE R. H. COULOUMA,
ARGENTEUIL
nrf

*** END OF THE PROJECT GUTENBERG EBOOK LE JARDINIER
D'AMOUR ***
Updated editions will replace the previous one—the old editions will
be renamed.
Creating the works from print editions not protected by U.S.
copyright law means that no one owns a United States copyright in
these works, so the Foundation (and you!) can copy and distribute it
in the United States without permission and without paying
copyright royalties. Special rules, set forth in the General Terms of
Use part of this license, apply to copying and distributing Project
Gutenberg™ electronic works to protect the PROJECT GUTENBERG™
concept and trademark. Project Gutenberg is a registered trademark,
and may not be used if you charge for an eBook, except by following
the terms of the trademark license, including paying royalties for use
of the Project Gutenberg trademark. If you do not charge anything
for copies of this eBook, complying with the trademark license is
very easy. You may use this eBook for nearly any purpose such as
creation of derivative works, reports, performances and research.
Project Gutenberg eBooks may be modified and printed and given
away—you may do practically ANYTHING in the United States with
eBooks not protected by U.S. copyright law. Redistribution is subject
to the trademark license, especially commercial redistribution.
START: FULL LICENSE

THE FULL PROJECT GUTENBERG LICENSE

PLEASE READ THIS BEFORE YOU DISTRIBUTE OR USE THIS WORK
To protect the Project Gutenberg™ mission of promoting the free
distribution of electronic works, by using or distributing this work (or
any other work associated in any way with the phrase “Project
Gutenberg”), you agree to comply with all the terms of the Full
Project Gutenberg™ License available with this file or online at
www.gutenberg.org/license.
Section 1. General Terms of Use and
Redistributing Project Gutenberg™
electronic works
1.A. By reading or using any part of this Project Gutenberg™
electronic work, you indicate that you have read, understand, agree
to and accept all the terms of this license and intellectual property
(trademark/copyright) agreement. If you do not agree to abide by all
the terms of this agreement, you must cease using and return or
destroy all copies of Project Gutenberg™ electronic works in your
possession. If you paid a fee for obtaining a copy of or access to a
Project Gutenberg™ electronic work and you do not agree to be
bound by the terms of this agreement, you may obtain a refund
from the person or entity to whom you paid the fee as set forth in
paragraph 1.E.8.
1.B. “Project Gutenberg” is a registered trademark. It may only be
used on or associated in any way with an electronic work by people
who agree to be bound by the terms of this agreement. There are a
few things that you can do with most Project Gutenberg™ electronic
works even without complying with the full terms of this agreement.
See paragraph 1.C below. There are a lot of things you can do with
Project Gutenberg™ electronic works if you follow the terms of this
agreement and help preserve free future access to Project
Gutenberg™ electronic works. See paragraph 1.E below.

1.C. The Project Gutenberg Literary Archive Foundation (“the
Foundation” or PGLAF), owns a compilation copyright in the
collection of Project Gutenberg™ electronic works. Nearly all the
individual works in the collection are in the public domain in the
United States. If an individual work is unprotected by copyright law
in the United States and you are located in the United States, we do
not claim a right to prevent you from copying, distributing,
performing, displaying or creating derivative works based on the
work as long as all references to Project Gutenberg are removed. Of
course, we hope that you will support the Project Gutenberg™
mission of promoting free access to electronic works by freely
sharing Project Gutenberg™ works in compliance with the terms of
this agreement for keeping the Project Gutenberg™ name associated
with the work. You can easily comply with the terms of this
agreement by keeping this work in the same format with its attached
full Project Gutenberg™ License when you share it without charge
with others.
1.D. The copyright laws of the place where you are located also
govern what you can do with this work. Copyright laws in most
countries are in a constant state of change. If you are outside the
United States, check the laws of your country in addition to the
terms of this agreement before downloading, copying, displaying,
performing, distributing or creating derivative works based on this
work or any other Project Gutenberg™ work. The Foundation makes
no representations concerning the copyright status of any work in
any country other than the United States.
1.E. Unless you have removed all references to Project Gutenberg:
1.E.1. The following sentence, with active links to, or other
immediate access to, the full Project Gutenberg™ License must
appear prominently whenever any copy of a Project Gutenberg™
work (any work on which the phrase “Project Gutenberg” appears,
or with which the phrase “Project Gutenberg” is associated) is
accessed, displayed, performed, viewed, copied or distributed:

This eBook is for the use of anyone anywhere in the United
States and most other parts of the world at no cost and with
almost no restrictions whatsoever. You may copy it, give it away
or re-use it under the terms of the Project Gutenberg License
included with this eBook or online at www.gutenberg.org. If you
are not located in the United States, you will have to check the
laws of the country where you are located before using this
eBook.
1.E.2. If an individual Project Gutenberg™ electronic work is derived
from texts not protected by U.S. copyright law (does not contain a
notice indicating that it is posted with permission of the copyright
holder), the work can be copied and distributed to anyone in the
United States without paying any fees or charges. If you are
redistributing or providing access to a work with the phrase “Project
Gutenberg” associated with or appearing on the work, you must
comply either with the requirements of paragraphs 1.E.1 through
1.E.7 or obtain permission for the use of the work and the Project
Gutenberg™ trademark as set forth in paragraphs 1.E.8 or 1.E.9.
1.E.3. If an individual Project Gutenberg™ electronic work is posted
with the permission of the copyright holder, your use and distribution
must comply with both paragraphs 1.E.1 through 1.E.7 and any
additional terms imposed by the copyright holder. Additional terms
will be linked to the Project Gutenberg™ License for all works posted
with the permission of the copyright holder found at the beginning
of this work.
1.E.4. Do not unlink or detach or remove the full Project
Gutenberg™ License terms from this work, or any files containing a
part of this work or any other work associated with Project
Gutenberg™.
1.E.5. Do not copy, display, perform, distribute or redistribute this
electronic work, or any part of this electronic work, without
prominently displaying the sentence set forth in paragraph 1.E.1

with active links or immediate access to the full terms of the Project
Gutenberg™ License.
1.E.6. You may convert to and distribute this work in any binary,
compressed, marked up, nonproprietary or proprietary form,
including any word processing or hypertext form. However, if you
provide access to or distribute copies of a Project Gutenberg™ work
in a format other than “Plain Vanilla ASCII” or other format used in
the official version posted on the official Project Gutenberg™ website
(www.gutenberg.org), you must, at no additional cost, fee or
expense to the user, provide a copy, a means of exporting a copy, or
a means of obtaining a copy upon request, of the work in its original
“Plain Vanilla ASCII” or other form. Any alternate format must
include the full Project Gutenberg™ License as specified in
paragraph 1.E.1.
1.E.7. Do not charge a fee for access to, viewing, displaying,
performing, copying or distributing any Project Gutenberg™ works
unless you comply with paragraph 1.E.8 or 1.E.9.
1.E.8. You may charge a reasonable fee for copies of or providing
access to or distributing Project Gutenberg™ electronic works
provided that:
• You pay a royalty fee of 20% of the gross profits you derive
from the use of Project Gutenberg™ works calculated using the
method you already use to calculate your applicable taxes. The
fee is owed to the owner of the Project Gutenberg™ trademark,
but he has agreed to donate royalties under this paragraph to
the Project Gutenberg Literary Archive Foundation. Royalty
payments must be paid within 60 days following each date on
which you prepare (or are legally required to prepare) your
periodic tax returns. Royalty payments should be clearly marked
as such and sent to the Project Gutenberg Literary Archive
Foundation at the address specified in Section 4, “Information

about donations to the Project Gutenberg Literary Archive
Foundation.”
• You provide a full refund of any money paid by a user who
notifies you in writing (or by e-mail) within 30 days of receipt
that s/he does not agree to the terms of the full Project
Gutenberg™ License. You must require such a user to return or
destroy all copies of the works possessed in a physical medium
and discontinue all use of and all access to other copies of
Project Gutenberg™ works.
• You provide, in accordance with paragraph 1.F.3, a full refund of
any money paid for a work or a replacement copy, if a defect in
the electronic work is discovered and reported to you within 90
days of receipt of the work.
• You comply with all other terms of this agreement for free
distribution of Project Gutenberg™ works.
1.E.9. If you wish to charge a fee or distribute a Project Gutenberg™
electronic work or group of works on different terms than are set
forth in this agreement, you must obtain permission in writing from
the Project Gutenberg Literary Archive Foundation, the manager of
the Project Gutenberg™ trademark. Contact the Foundation as set
forth in Section 3 below.
1.F.
1.F.1. Project Gutenberg volunteers and employees expend
considerable effort to identify, do copyright research on, transcribe
and proofread works not protected by U.S. copyright law in creating
the Project Gutenberg™ collection. Despite these efforts, Project
Gutenberg™ electronic works, and the medium on which they may
be stored, may contain “Defects,” such as, but not limited to,
incomplete, inaccurate or corrupt data, transcription errors, a
copyright or other intellectual property infringement, a defective or

damaged disk or other medium, a computer virus, or computer
codes that damage or cannot be read by your equipment.
1.F.2. LIMITED WARRANTY, DISCLAIMER OF DAMAGES - Except for
the “Right of Replacement or Refund” described in paragraph 1.F.3,
the Project Gutenberg Literary Archive Foundation, the owner of the
Project Gutenberg™ trademark, and any other party distributing a
Project Gutenberg™ electronic work under this agreement, disclaim
all liability to you for damages, costs and expenses, including legal
fees. YOU AGREE THAT YOU HAVE NO REMEDIES FOR
NEGLIGENCE, STRICT LIABILITY, BREACH OF WARRANTY OR
BREACH OF CONTRACT EXCEPT THOSE PROVIDED IN PARAGRAPH
1.F.3. YOU AGREE THAT THE FOUNDATION, THE TRADEMARK
OWNER, AND ANY DISTRIBUTOR UNDER THIS AGREEMENT WILL
NOT BE LIABLE TO YOU FOR ACTUAL, DIRECT, INDIRECT,
CONSEQUENTIAL, PUNITIVE OR INCIDENTAL DAMAGES EVEN IF
YOU GIVE NOTICE OF THE POSSIBILITY OF SUCH DAMAGE.
1.F.3. LIMITED RIGHT OF REPLACEMENT OR REFUND - If you
discover a defect in this electronic work within 90 days of receiving
it, you can receive a refund of the money (if any) you paid for it by
sending a written explanation to the person you received the work
from. If you received the work on a physical medium, you must
return the medium with your written explanation. The person or
entity that provided you with the defective work may elect to provide
a replacement copy in lieu of a refund. If you received the work
electronically, the person or entity providing it to you may choose to
give you a second opportunity to receive the work electronically in
lieu of a refund. If the second copy is also defective, you may
demand a refund in writing without further opportunities to fix the
problem.
1.F.4. Except for the limited right of replacement or refund set forth
in paragraph 1.F.3, this work is provided to you ‘AS-IS’, WITH NO
OTHER WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED,

INCLUDING BUT NOT LIMITED TO WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR ANY PURPOSE.
1.F.5. Some states do not allow disclaimers of certain implied
warranties or the exclusion or limitation of certain types of damages.
If any disclaimer or limitation set forth in this agreement violates the
law of the state applicable to this agreement, the agreement shall be
interpreted to make the maximum disclaimer or limitation permitted
by the applicable state law. The invalidity or unenforceability of any
provision of this agreement shall not void the remaining provisions.
1.F.6. INDEMNITY - You agree to indemnify and hold the Foundation,
the trademark owner, any agent or employee of the Foundation,
anyone providing copies of Project Gutenberg™ electronic works in
accordance with this agreement, and any volunteers associated with
the production, promotion and distribution of Project Gutenberg™
electronic works, harmless from all liability, costs and expenses,
including legal fees, that arise directly or indirectly from any of the
following which you do or cause to occur: (a) distribution of this or
any Project Gutenberg™ work, (b) alteration, modification, or
additions or deletions to any Project Gutenberg™ work, and (c) any
Defect you cause.
Section 2. Information about the Mission
of Project Gutenberg™
Project Gutenberg™ is synonymous with the free distribution of
electronic works in formats readable by the widest variety of
computers including obsolete, old, middle-aged and new computers.
It exists because of the efforts of hundreds of volunteers and
donations from people in all walks of life.
Volunteers and financial support to provide volunteers with the
assistance they need are critical to reaching Project Gutenberg™’s
goals and ensuring that the Project Gutenberg™ collection will

remain freely available for generations to come. In 2001, the Project
Gutenberg Literary Archive Foundation was created to provide a
secure and permanent future for Project Gutenberg™ and future
generations. To learn more about the Project Gutenberg Literary
Archive Foundation and how your efforts and donations can help,
see Sections 3 and 4 and the Foundation information page at
www.gutenberg.org.
Section 3. Information about the Project
Gutenberg Literary Archive Foundation
The Project Gutenberg Literary Archive Foundation is a non-profit
501(c)(3) educational corporation organized under the laws of the
state of Mississippi and granted tax exempt status by the Internal
Revenue Service. The Foundation’s EIN or federal tax identification
number is 64-6221541. Contributions to the Project Gutenberg
Literary Archive Foundation are tax deductible to the full extent
permitted by U.S. federal laws and your state’s laws.
The Foundation’s business office is located at 809 North 1500 West,
Salt Lake City, UT 84116, (801) 596-1887. Email contact links and up
to date contact information can be found at the Foundation’s website
and official page at www.gutenberg.org/contact
Section 4. Information about Donations to
the Project Gutenberg Literary Archive
Foundation
Project Gutenberg™ depends upon and cannot survive without
widespread public support and donations to carry out its mission of
increasing the number of public domain and licensed works that can
be freely distributed in machine-readable form accessible by the
widest array of equipment including outdated equipment. Many

small donations ($1 to $5,000) are particularly important to
maintaining tax exempt status with the IRS.
The Foundation is committed to complying with the laws regulating
charities and charitable donations in all 50 states of the United
States. Compliance requirements are not uniform and it takes a
considerable effort, much paperwork and many fees to meet and
keep up with these requirements. We do not solicit donations in
locations where we have not received written confirmation of
compliance. To SEND DONATIONS or determine the status of
compliance for any particular state visit www.gutenberg.org/donate.
While we cannot and do not solicit contributions from states where
we have not met the solicitation requirements, we know of no
prohibition against accepting unsolicited donations from donors in
such states who approach us with offers to donate.
International donations are gratefully accepted, but we cannot make
any statements concerning tax treatment of donations received from
outside the United States. U.S. laws alone swamp our small staff.
Please check the Project Gutenberg web pages for current donation
methods and addresses. Donations are accepted in a number of
other ways including checks, online payments and credit card
donations. To donate, please visit: www.gutenberg.org/donate.
Section 5. General Information About
Project Gutenberg™ electronic works
Professor Michael S. Hart was the originator of the Project
Gutenberg™ concept of a library of electronic works that could be
freely shared with anyone. For forty years, he produced and
distributed Project Gutenberg™ eBooks with only a loose network of
volunteer support.

Project Gutenberg™ eBooks are often created from several printed
editions, all of which are confirmed as not protected by copyright in
the U.S. unless a copyright notice is included. Thus, we do not
necessarily keep eBooks in compliance with any particular paper
edition.
Most people start at our website which has the main PG search
facility: www.gutenberg.org.
This website includes information about Project Gutenberg™,
including how to make donations to the Project Gutenberg Literary
Archive Foundation, how to help produce our new eBooks, and how
to subscribe to our email newsletter to hear about new eBooks.

Welcome to our website – the perfect destination for book lovers and
knowledge seekers. We believe that every book holds a new world,
offering opportunities for learning, discovery, and personal growth.
That’s why we are dedicated to bringing you a diverse collection of
books, ranging from classic literature and specialized publications to
self-development guides and children's books.
More than just a book-buying platform, we strive to be a bridge
connecting you with timeless cultural and intellectual values. With an
elegant, user-friendly interface and a smart search system, you can
quickly find the books that best suit your interests. Additionally,
our special promotions and home delivery services help you save time
and fully enjoy the joy of reading.
Join us on a journey of knowledge exploration, passion nurturing, and
personal growth every day!
testbankfan.com

Database Systems Design Implementation and Management 11th Edition Coronel Solutions Manual

Recommended

More Related Content

Similar to Database Systems Design Implementation and Management 11th Edition Coronel Solutions Manual (20)

Recently uploaded (20)

Database Systems Design Implementation and Management 11th Edition Coronel Solutions Manual