SQL and relational theory how to write accurate SQL code 2ed. Edition Date - The complete ebook is available for download with one click
SQL and relational theory how to write accurate SQL code 2ed. Edition Date - The complete ebook is available for download with one click
https://ebookultra.com/download/sql-and-relational-theory-how-to-
write-accurate-sql-code-1st-edition-c-j-date/
https://ebookultra.com/download/the-language-of-sql-how-to-access-
data-in-relational-databases-1st-edition-larry-rockoff/
https://ebookultra.com/download/relational-theory-for-computer-
professionals-1st-edition-c-j-date/
https://ebookultra.com/download/database-in-depth-relational-theory-
for-practitioners-1st-edition-c-j-date/
SQL Server T SQL Recipes 4th Edition Jason Brimhall
https://ebookultra.com/download/sql-server-t-sql-recipes-4th-edition-
jason-brimhall/
https://ebookultra.com/download/microsoft-sql-server-2012-t-sql-1st-
edition-tom-coffing/
https://ebookultra.com/download/essential-sql-on-sql-server-2008-1st-
edition-dr-sikha-bagui/
https://ebookultra.com/download/joe-celko-s-sql-for-smarties-fourth-
edition-advanced-sql-programming-joe-celko/
https://ebookultra.com/download/inside-microsoft-sql-
server-2008-t-sql-querying-1st-edition-itzik-ben-gan/
SQL and relational theory how to write accurate SQL
code 2ed. Edition Date Digital Instant Download
Author(s): Date, C. J
ISBN(s): 9781449319755, 1449319750
Edition: 2ed.
File Details: PDF, 6.61 MB
Year: 2012
Language: english
SQL and
Relational Theory
SECOND EDITION
C. J. Date
O’Reilly books may be purchased for educational, business, or sales promotional use. Online editions are also
available for most titles (http://my.safaribooksonline.com). For more information, contact our corporate/institutional
sales department: (800) 998-9938 or [email protected].
Printing History:
January 2009: First Edition.
December 2011: Second Edition.
Revision History:
2011-12-08 First release
See http://oreilly.com/catalog/errata.csp?isbn= 9781449316402 for release details.
Nutshell Handbook, the Nutshell Handbook logo, and the O’Reilly logo are registered trademarks of
O’Reilly Media, Inc. SQL and Relational Theory: How to Write Accurate SQL Code and related trade dress are
trademarks of O’Reilly Media, Inc.
Many of the designations used by manufacturers and sellers to distinguish their products are claimed as
trademarks. Where those designations appear in this book, and O’Reilly Media, Inc., was aware of a
trademark claim, the designations have been printed in caps or initial caps.
While every precaution has been taken in the preparation of this book, the publisher and authors assume
no responsibility for errors or omissions, or for damages resulting from the use of the information contained
herein.
ISBN: 978-1-449-31640-2
[LSI]
Languages die...
mathematical ideas do not.
—G. H. Hardy (1877–1947)
C. J. Date is an independent author, lecturer, researcher, and consultant, specializing in relational database
technology. He is best known for his book An Introduction to Database Systems, 8th edition (Addison-Wesley,
2004), which has sold some 850,000 copies at the time of writing and is used by several hundred colleges and
universities worldwide. He is also the author of many other books on database management, including most
recently:
From Addison-Wesley: Databases, Types, and the Relational Model: The Third Manifesto, 3rd edition
(coauthored with Hugh Darwen, 2006)
From Trafford: Logic and Databases: The Roots of Relational Theory (2007)
From Trafford: Database Explorations: Essays on The Third Manifesto and Related Topics (coauthored with
Hugh Darwen, 2010)
Another book, Normal Forms and All That Jazz: A Database Professional’s Guide to Database Design Theory (a
companion to the present book), is also due for publication in the near future.
Mr. Date was inducted into the Computing Industry Hall of Fame in 2004. He enjoys a reputation that is
second to none for his ability to explain complex technical subjects in a clear and understandable fashion.
What’s a tuple? 49
Rows in SQL 53
What’s a relation? 55
Relations and their bodies 57
Relations are n-dimensional 58
Relational comparisons 58
TABLE_DUM and TABLE_DEE 59
Tables in SQL 60
SELECT * 273
Explicit tables 274
Name qualification 274
Range variables 275
Subqueries 277
“Possibly nondeterministic” expressions 280
Empty sets 281
A simplified BNF grammar 281
Exercises 285
Queries 314
More on predicates 317
Exercises 320
Chapter 1 329
Chapter 2 335
Chapter 3 341
Chapter 4 346
Chapter 5 352
Chapter 6 358
Chapter 7 366
Chapter 8 379
Chapter 9 389
Chapter 10 395
Chapter 11 403
Chapter 12 405
Appendix C 407
Index 419
SQL is ubiquitous. But SQL is hard to use: It’s complicated, confusing, and error prone (much more so, I venture to
suggest, than its apologists would have you believe). In order to have any hope of writing SQL code that you can be
sure is accurate, therefore—meaning it does exactly what it’s supposed to do, no more and no less—you must follow
some appropriate discipline. And it’s the thesis of this book that using SQL relationally is the discipline you need.
But what does this mean? Isn’t SQL relational anyway?
Well, it’s true that SQL is the standard language for use with relational databases—but that fact in itself
doesn’t make it relational. The sad truth is, SQL departs from relational theory in all too many ways; duplicate rows
and nulls are two obvious examples, but they’re not the only ones. As a consequence, the language gives you rope to
hang yourself with, as it were. So if you don’t want to hang yourself, you need to understand relational theory (what
it is and why); you need to know about SQL’s departures from that theory; and you need to know how to avoid the
problems they can cause. In a word, you need to use SQL relationally. Then you can behave as if SQL truly were
relational, and you can enjoy the benefits of working with what is, in effect, a truly relational system.
Now, a book like this wouldn’t be needed if everyone was using SQL relationally already—but they aren’t.
On the contrary, I observe much bad practice in current SQL usage. I even observe such practice being
recommended, in textbooks and similar publications, by writers who really ought to know better (no names, no pack
drill); in fact, a review of the literature in this regard is a pretty dispiriting exercise. The relational model first saw
the light of day in 1969, and yet here we are, over 40 years later, and it still doesn’t seem to be very well understood
by the database community at large. Partly for such reasons, this book uses the relational model itself as an
organizing principle; it explains various features of the model in depth, and shows in every case how best to use
SQL in order to comply with the feature in question.
Prerequisites
I assume you’re a database practitioner and therefore reasonably familiar with SQL already. To be specific, I assume
you have a working knowledge of either the SQL standard or (perhaps more likely in practice) at least one SQL
product. However, I don’t assume you have a deep knowledge of relational theory as such (though I do hope you
understand that the relational model is a good thing in general, and adherence to it wherever possible is a desirable
goal). In order to avoid misunderstandings, therefore, I’ll be describing various features of the relational model in
detail, as well as showing how to use SQL to conform to those features. But what I won’t do is attempt to justify all
of those features; rather, I’ll assume you’re sufficiently experienced in database matters to understand why, e.g., the
notion of a key makes sense, or why you sometimes need to do a join, or why many to many relationships need to be
supported. (If I were to include such justifications, this would be a very different book—quite apart from anything
else, it would be much bigger than it already is—and in any case, that book has already been written.)
I’ve said I expect you to be reasonably familiar with SQL. However, I should add that I’ll be explaining
certain aspects of SQL in detail anyway—especially aspects that might be encountered less frequently in practice.
(The SQL notion of possibly nondeterministic expressions is a case in point here. See Chapter 12.)
Database in Depth
This book is based on, and intended to replace, an earlier one with the title Database in Depth: Relational Theory
for Practitioners (O’Reilly Media Inc., 2005). My aim in that earlier book was as follows (this is a quote from the
preface):
After many years working in the database community in various capacities, I’ve come to realize there’s a real need for a
book for practitioners (not novices) that explains the basic principles of relational theory in a way not tainted by the
quirks and peculiarities of existing products, commercial practice, or the SQL standard. I wrote this book to fill that need.
My intended audience is thus experienced database practitioners who are honest enough to admit they don’t understand
the theory underlying their own field as well as they might, or should. That theory is, of course, the relational model—
and while it’s true that the fundamental ideas of that theory are all quite simple, it’s also true that they’re widely
misrepresented, or underappreciated, or both. Often, in fact, they don’t seem to be understood at all. For example, here
are a few relational questions ... How many of them can you answer?1
This book provides answers to these and many related questions. Overall, it’s meant to help database practitioners
understand relational theory in depth and make good use of that understanding in their professional day-to-day activities.
As the final sentence in this extract indicates, it was my hope that readers of that book would be able to apply
its ideas for themselves, without further assistance from me as it were. But I’ve since come to realize that, contrary
to popular opinion, SQL is such a difficult language that it can be far from obvious how to use it without violating
relational principles. I therefore decided to expand the original book to include explicit, concrete advice on exactly
that issue (how to use SQL relationally, I mean). So my aim in the present book is still the same as before—I want to
help database practitioners understand relational theory in depth and make good use of that understanding in their
professional activities—but I’ve tried to make the material a little easier to digest, perhaps, and certainly easier to
apply. In other words, I’ve included a great deal of SQL-specific material (and it’s this fact, more than anything else,
that accounts for the increase in size over the previous book).
I need to take care of several further preliminaries. First of all, my own understanding of the relational model has
evolved over the years, and continues to do so. This book represents my very latest thinking on the subject; thus, if
you detect any technical discrepancies—and there are a few—between this book and other books you might have
seen by myself (including in particular the one the present book is meant to replace), the present book should be
taken as superseding. Though I hasten to add that such discrepancies are mostly of a fairly minor nature; what’s
more, I’ve taken care always to relate new terms and concepts to earlier ones, wherever I felt it was necessary to do
so.
Second, I will, as advertised, be talking about theory—but it’s an article of faith with me that theory is
practical. I mention this point explicitly because so many seem to believe the opposite: namely, that if something’s
1
For reasons that aren’t important here, I’ve replaced a few of the questions in this list by new ones.
theoretical, it can’t be practical. But the truth is that theory (at least, relational theory, which is what I’m talking
about here) is most definitely very practical indeed. The purpose of that theory is not just theory for its own sake; the
purpose of that theory is to allow us to build systems that are 100 percent practical. Every detail of the theory is
there for solid practical reasons. As Stéphane Faroult, a reviewer of the earlier book, wrote: “When you have a bit
of practice, you realize there’s no way to avoid having to know the theory.” What’s more, that theory is not only
practical, it’s fundamental, straightforward, simple, useful, and it can be fun (as I hope to demonstrate in the course
of this book).
Of course, we really don’t have to look any further than the relational model itself to find the most striking
possible illustration of the foregoing thesis. Indeed, it really shouldn’t be necessary to have to defend the notion that
theory is practical, in a context such as ours: namely, a multibillion dollar industry totally founded on one great
theoretical idea. But I suppose the cynic’s position would be “Yes, but what has theory done for me lately?” In
other words, those of us who do think theory is important must continually be justifying ourselves to our critics—
which is another reason why I think a book like this one is needed.
Third, as I’ve said, the book does go into a fair amount of detail regarding features of SQL or the relational
model or both. (It deliberately has little to say on topics that aren’t particularly relational; for example, there isn’t
much on transactions.) Throughout, I’ve tried to make it clear when the discussions apply to SQL specifically, when
they apply to the relational model specifically, and when they apply to both. I should emphasize, however, that the
SQL discussions in particular aren’t meant to be exhaustive. SQL is such a complex language, and provides so many
different ways of doing the same thing, and is subject to so many exceptions and special cases, that to be
exhaustive—even if it were possible, which I tend to doubt—would be counterproductive; certainly it would make
the book much too long. So I’ve tried to focus on what I think are the most important issues, and I’ve tried to be as
brief as possible on the issues I’ve chosen to cover. And I’d like to claim that if you do everything I tell you, and
don’t do anything I don’t tell you, then to a first approximation you’ll be safe: You’ll be using SQL relationally. But
whether that claim is justified, or to what extent it is, must be for you to judge.
To the foregoing I have to add that, unfortunately, there are some situations in which SQL just can’t be used
relationally. For example, some SQL integrity checking simply has to be deferred (usually to commit time), even
though the relational model explicitly rejects such checking as logically flawed. The book does offer advice on what
to do in such cases, but I fear it often boils down to just Do the best you can. At least I hope you’ll understand the
risks involved in departing from the model.
I should say too that some of the recommendations offered aren’t specifically relational anyway but are,
rather, just matters of general good practice—though sometimes there are relational implications (implications that
can be a little unobvious, too, perhaps I should add). Avoid coercions is a good example here.
Fourth, please note that I use the term SQL throughout the book to mean the standard version of that
language exclusively, not some proprietary dialect, barring explicit statements to the contrary. In particular, I follow
the standard in assuming the pronunciation “ess cue ell,” not “sequel” (though this latter is common in the field),
thereby saying things like an SQL table, not a SQL table.
Fifth, the book is meant to be read in sequence, pretty much, except as noted here and there in the text itself
(most of the chapters do rely to some extent on material covered in earlier ones, so you shouldn’t jump around too
much). Also, each chapter includes a set of exercises. You don’t have to do those exercises, of course, but I think it’s
a good idea to have a go at some of them at least. Answers, often giving more information about the subject at hand,
are given in Appendix F.
Finally, I’d like to mention that I have some live seminars available based on the material in this book. See
www.justsql.co.uk/chris_date/chris_date.htm or www.thethirdmanifesto.com for further details. An online version of
one of those seminars is available too, at http://oreilly.com/catalog/0636920010005/.
We appreciate, but do not require, attribution. An attribution usually includes the title, author, publisher, and ISBN.
For example: “SQL and Relational Theory, Second Edition, by C.J. Date (O’Reilly). Copyright 2012 C.J. Date,
9781449316402.”
If you feel your use of code examples falls outside fair use or the permission given above, feel free to contact us at
[email protected].
We have a web page for this book, where we list errata, examples, and any additional information. You can access
this page at http://shop.oreilly.com/product/0636920022879.do.
To comment or ask technical questions about this book, send email to [email protected].
For more information about our books, courses, conferences, and news, see our website at http://www.oreilly.com.
With a subscription, you can read any page and watch any video from our library online. Read books on your cell
phone and mobile devices. Access new titles before they are available for print, and get exclusive access to
manuscripts in development and post feedback for the authors. Copy and paste code samples, organize your
favorites, download chapters, bookmark key sections, create notes, print out pages, and benefit from tons of other
time-saving features.
O’Reilly Media has uploaded this book to the Safari Books Online service. To have full digital access to this book
and others on similar topics from O’Reilly and other publishers, sign up for free at http://my.safaribooksonline.com.
Acknowledgments
I’d been thinking for some time about revising the earlier book to include more on SQL in particular, but the spur
that finally got me down to it was sitting in on a class, late in 2007, for database practitioners. The class was taught
by Toon Koppelaars and was based on the book he wrote with Lex de Haan (see Appendix G of the present book),
and very good it was, too. But what struck me most about that class was seeing firsthand the kinds of difficulties the
attendees had in applying relational and logical principles to their use of SQL. Now, I do assume those attendees had
some knowledge of those topics—they were database practitioners, after all—but it seemed to me they really needed
some guidance in the application of those ideas to their daily database activities. And so I put this book together. So
I’m thankful, first of all, to Toon and Lex for providing me with the necessary impetus to get started on this project.
I’m grateful also to my reviewers Herb Edelstein, Sheeri Ktitzer, Andy Oram, Peter Robson, and Baron Schwartz for
their comments on earlier drafts, and Hugh Darwen and Jim Melton for other technical assistance. Next, I’d like to
thank my wife Lindy, as always, for her support throughout this and all of my other database projects over the years.
Finally, I’m grateful to everyone at O’Reilly—especially Isabel Kunkle and Andy Oram—for their encouragement,
contributions, and support throughout the production of this book.
C. J. Date
Healdsburg, California
2008
This edition differs from its predecessor in a number of ways. The overall objective remains the same, of course—
using SQL relationally is still the emphasis—but the text has been revised throughout to reflect, among other things,
experience gained from teaching live seminars based on the first edition.
One significant change is a deletion: The appendix on design theory has gone. There are two reasons for this
change. First, design theory as such never really did have all that much to do with the book’s main message,
anyway; second, the appendix was getting so extensive that it threatened to overwhelm the rest of the text. (It was
already longer than any chapter or any other appendix in the book. In fact, I’ve since expanded the material into a
separate book in its own right. That book—Normal Forms and All That Jazz: A Database Professional’s Guide to
Database Design Theory—is due to be published soon by O’Reilly. It can be seen as a companion, or perhaps a
sequel, to the present book.)
On the positive side, a lot of new material has been added (including, importantly, a discussion of how to
deal with missing information without using nulls); examples, exercises, and answers have been expanded and
improved in various respects; and the treatment of SQL has been upgraded to cover recent changes to the SQL
standard. A variety of corrections and numerous cosmetic improvements have also been made.2 (In particular, the
Tutorial D examples—Tutorial D being the language I use to illustrate relational concepts—have been upgraded to
reflect several recent improvements to that language. See Appendix D.) The net effect is to make the text rather
more comprehensive—but, sadly, some 25 percent bigger—than its predecessor.
Talking of the text, I’d like to say something about my use of footnotes. Frankly, I’m rather embarrassed at
how many footnotes there are; I’m well aware how annoying they can be—indeed, they can seriously impede
readability. But any text dealing with SQL is more or less forced into a heavy use of footnotes, at least if it wants to
be tutorial in nature and yet reasonably comprehensive at the same time. The reason is that SQL involves so many
inconsistencies, exceptions, and special cases that treating everything “in line”—i.e., at the same level of
description—makes it very difficult to see the forest for the trees. (Indeed, this is one reason why the SQL standard
itself is so difficult to understand.) Thus, there are numerous places in the book where the major idea is described
“in line” in the main body of the text, and exceptions and the like (which must at least be mentioned, for reasons of
accuracy and completeness) are relegated to a footnote. It might be best simply to ignore all footnotes on a first
reading.
C. J. Date
Healdsburg, California
2012
2
In this connection, I’d like to acknowledge the contribution of a reader of the first edition, Thomas Uhren, who found an embarrassingly large
number of errors. I’ll try harder in future. I promise.
A relational approach to SQL: That’s the theme, or one of the themes, of this book. Of course, to treat such a topic
adequately, I need to cover relational issues as well as issues of SQL per se─and while this remark obviously applies
to the book as a whole, it applies to this first chapter with special force. As a consequence, this chapter has
comparatively little to say about SQL as such. What I want to do is review material that for the most part, at any
rate, I hope you already know. My intent is to establish a point of departure, as it were: in other words, to lay some
groundwork on which the rest of the book can build. But even though I hope you’re familiar with most of what I
have to say in this chapter, I’d like to suggest, respectfully, that you not skip it. You need to know what you need to
know (if you see what I mean); in particular, you need to be sure you have the prerequisites needed to understand
the material to come in later chapters. In fact I’d like to recommend, politely, that throughout the book you not skip
the discussion of some topic just because you think you’re familiar with that topic already. For example, are you
absolutely sure you know what a key is, in relational terms? Or a join?1
Professionals in any discipline need to know the foundations of their field. So if you’re a database professional, you
need to know the relational model, because the relational model is the foundation (or a large part of the foundation,
at any rate) of the database field in particular. Now, every course in database management, be it academic or
commercial, does at least pay lip service to the idea of teaching the relational model─but most of that teaching
seems to be done very badly, if results are anything to go by. Certainly the model isn’t well understood in the
database community at large. Here are some possible reasons for this state of affairs:
The model is taught in a vacuum. That is, for beginners at least, it’s hard to see the relevance of the material,
or it’s hard to understand the problems it’s meant to solve, or both.
The instructors themselves don’t fully understand or appreciate the significance of the material.
1
There’s at least one pundit who doesn’t. The following is a direct quote from a document purporting (like this book!) to offer advice to SQL
users: “Don’t use joins ... Oracle and SQL Server have fundamentally different approaches to the concept ... You can end up with unexpected
result sets ... You should understand the basic types of join clauses ... Equijoins are formed by retrieving all the data from two separate sources
and combining it into one, large table ... Inner joins are joined on the inner columns of two tables. Outer joins are joined on the outer columns of
two tables. Left joins are joined on the left columns of two tables. Right joins are joined on the right columns of two tables.”
Perhaps most likely in practice, the model as such isn’t taught at all─the SQL language, or some specific
dialect of that language, such as the Oracle dialect, is taught instead.
So this book is aimed at database practitioners in general, and SQL practitioners in particular, who have had
some exposure to the relational model but don’t know as much about it as they ought to, or would like to. It’s
definitely not meant for beginners; however, it isn’t just a refresher course, either. To be more specific, I’m sure
you know something about SQL; but─and I apologize for the possibly offensive tone here─if your knowledge of the
relational model derives only from your knowledge of SQL, then I’m afraid you won’t know the relational model as
well as you should, and you’ll probably know “some things that ain’t so.” I can’t say it too strongly: SQL and the
relational model aren’t the same thing. Here by way of illustration are some relational issues that SQL isn’t too
clear on (to put it mildly):
and so on (this isn’t an exhaustive list). All of these issues, and many others, are addressed in this book.
I say again: If your knowledge of the relational model derives only from your knowledge of SQL, then you
might know “some things that ain’t so.” One consequence is that you might find, in reading this book, that you have
to do some unlearning─and unlearning, unfortunately, is very hard to do.
You probably noticed right away, in that bullet list of relational issues in the previous section, that I used the formal
terms relation, tuple (usually pronounced to rhyme with couple), and attribute. SQL doesn’t use these terms, of
course─it uses the more “user friendly” terms table, row, and column instead. And I’m generally sympathetic to the
idea of using more user friendly terms, if they can help make the ideas more palatable. In the case at hand, however,
it seems to me that, regrettably, they don’t make the ideas more palatable; instead, they distort them, and in fact do
the cause of genuine understanding a grave disservice. The truth is, a relation is not a table, a tuple is not a row, and
an attribute is not a column. And while it might be acceptable to pretend otherwise in informal contexts─indeed, I
often do so myself─I would argue that it’s acceptable only if we all understand that the more user friendly terms are
just an approximation to the truth and fail overall to capture the essence of what’s really going on. To put it another
way: If you do understand the true state of affairs, then judicious use of the user friendly terms can be a good idea;
but in order to learn and appreciate that true state of affairs in the first place, you really do need to come to grips
with the formal terms. In this book, therefore, I’ll tend to use those formal terms (at least when I’m talking about the
relational model as opposed to SQL), and I’ll give precise definitions for them at the relevant juncture. In SQL
contexts, by contrast, I’ll use SQL’s own terms.
And another point on terminology: Having said that SQL tries to simplify one set of terms, I must say too
that it does its best to complicate another. I refer to its use of the terms operator, function, procedure, routine, and
The evidence of his own eyes was enough, and Jen replaced the
devil-stick upon the table, with the full conviction that the bag had
been filled with a fresh preparation of its original venom. This
discovery, to the major's mind, confirmed the guilt of the negress.
"What is the matter?" asked Lady Meg, as she saw the major's face
grow dark with his thought. "Is anything wrong?"
"Yes, Dido is wrong," he said. "I always thought that black witch was
at the bottom of everything. I am sure of it now."
"Dido!" repeated Lady Meg, thoughtfully. "I have heard Mr. Alymer
and Mr. Sarby talking about her. A negress, is she not?"
"Do you really think she killed him?" asked Lady Meg, her face
growing pale with the intensity of her excitement.
"I do," replied Jen, decisively. "But the evidence--ah, the evidence.
Well," he added, after a pause, "I have something to go on, in this
refilled devil-stick, and the saturated handkerchief."
"Never mind, my dear lady, you will later on," retorted Jen, with a
nod. Then turning to Battersea, he resumed his examination. "You
know the negress. Dido, who is in the employment of Mrs. Dallas?"
he asked, mildly.
"How so?"
"Well, sir." Battersea scratched his shock head. "She knows things as
ain't good for 'er. 'Bout that devil-stick es you talks of."
"Oh," cried Jen, recalling Dido's denial, "she knows of that, does
she?"
"Yes, sir, she do. Arsked me 'bout it, but I knowed nuffin, I didn't."
"Well, sir, when I brought a message from Dr. Etwald 'bout that
devil-stick--"
"What!" cried Jen, interrupting sharply. "Did Dr. Etwald know about it
also?"
"I ain't a fool, sir," said the tramp, with a sheepish grin. "I should,
you bet."
"In that case go down to the kitchen and tell my servants from me
that you are to stay there. Later on I'll see you."
"Thankee, sir. I'll get free quarters and grub for a week," cried
Battersea, rubbing his grimy hands. "My eye, 'ere's oppolance. Can I
go now, sir?"
"At once," replied Jen, and pointed to the door. Battersea bowed
awkwardly to Lady Meg and his benefactor; then he went out of the
room and left the major alone with his visitor.
"What does all this mean?" asked Meg, quite surprised at Jen's
excitement.
CHAPTER XVI.
"Mean? Death without the addition of life. That word was brought in
solely to render the prophecy--if it may be called so--confusing.
Etwald was in love with Miss Dallas. He found in Maurice a
formidable rival. He warned him by his pretended prophecy that he
should slay him if he persisted standing in his path. Maurice
announced his engagement upon the very day when Etwald, the
designing scoundrel, went to pay his addresses to the girl. From that
moment he doomed Maurice to death. Yes, I truly believe that such
was his design, and that he offered to buy the devil-stick in order to
carry out his criminal intention."
"Twice; and both times I refused to part with it. Failing to get it
honestly, he stole it."
"From the peculiar, sickly, heavy odor," explained Jen, promptly; and
continued: "Well, you can see the rest for yourself. Dido filled that
devil-stick with the poison," he pointed to the article on the table,
"some of it remains in the wand yet. Etwald used the devil-stick to
kill Maurice, and on going back to tell Dido of his success I have no
doubt he dropped it inside the gates of Mrs. Dallas' grounds, where,
as you have heard, it was found by Battersea. Oh, it is as plain as
day to me," cried Jen, vehemently. "Etwald killed Maurice and stole
the devil-stick to accomplish the murder."
"You have certainly made out a strong case against this man," said
Meg, after a pause, "but it is all theory. Your proofs?"
Lady Meg sighed, and rising to her feet, she drew her cloak round
her tall form.
"I shall help you also," she said sadly. "That is, if you will accept of
my help."
"To my cost, major; but he did not love me. This girl--this Miss
Dallas," she added in a faltering voice, "she must be very lovely, for
Mr. Sarby loves her also. A woman who has three men at her feet
must be wonderful."
"I should not think from your description that she was likely to
attract Maurice," said Lady Meg, in a low voice; "but undoubtedly he
loved her dearly; and I--" She made a gesture of despair and moved
toward the door. On the threshold she paused and held out her
hand. "Good-by, major; should I hear anything further I shall let you
know. But the tramp?"
"Or from Etwald," rejoined Jen. "If I can only succeed in having him
arrested he may confess all."
"Let us hope he will," replied Lady Meg, and after shaking hands
again with Jen, she took her departure.
When the major had seen her carriage drive away he returned to
look after the devil-stick, and examined it long and carefully.
Undoubtedly it had been filled with fresh poison, and undoubtedly
the poison, from the evidence heretofore set forth, had been
prepared by Dido. Jen was more certain than ever that Etwald and
the negress had stolen the devil-stick and had slain Maurice with it.
But the theft of the body! It was that which puzzled him. He could
understand why Etwald wanted Maurice removed from his path. He
could explain, on those grounds, why the devil-stick had been
stolen. But what reason could the pair have for the removal of the
body? The poor boy had died, and his corpse could be of no use to
those who had murdered him. Yet it had disappeared, and the only
person who could give any evidence as to who had entered the
room on that fatal night was Jaggard. But up to the present moment
Jaggard had remained incapable of giving any clear evidence.
Absolutely certain that Etwald was guilty, that Dido was an
accomplice, Jen could not see his way to proving his case without
the assistance of Jaggard.
While the major was thus considering what step he should take,
David, returning from a long and solitary walk, entered the room. Of
late the young man had indulged in these lonely excursions, whence
he always returned more melancholy than ever. His fine face was
lean and worn, there were dark circles under his eyes, and his
manner, formerly noted for its composure, was now nervous and
hesitating. On approaching his guardian he saw the devil-stick on
the table, and at once his pale face grew yet paler.
"Where did you find it?" he asked, pointing a trembling finger at the
terrible piece of evidence.
"I did not find it at all," rejoined the major, gloomily; "Lady Meg
brought it to me."
"And she--she----"
"She has nothing to do with the matter," replied Jen, surprised at the
agitation of the young man. "It was Battersea who found it. He
offered it for sale to Lady Meg, and she brought it and the tramp to
me."
"No. He found the devil-stick within the grounds of Mrs. Dallas, near
the gates."
"I think so; it is my belief, David, that Dr. Etwald killed Maurice!"
"In that case he should rather have killed me than poor Maurice, for,
as my suit to Isabella was supported by Mrs. Dallas, I was the more
formidable rival of the two."
"I don't think so, my boy. Isabella loved Maurice, and to marry him
she would have rebelled against her mother. But I daresay if you
become engaged to her, Etwald will remove you also from his path."
"There will be no need for him to do that," replied David, coldly. "I
shall never marry Isabella."
"I do love her," cried David, vehemently. "I have always loved her,
and shall continue to do so until the day of my death. All the same, I
shall never become her husband."
"Why?"
"Don't ask me, major. I would tell you if I could, but it is impossible."
"I would tell you if I could," said David again, but in rather a sullen
manner; "but I have reasons, strong reasons, for not doing so. Later
on--" he paused nervously.
"All you know!" repeated Jen, in a startled tone. "About this crime?"
"Yes. I know something, but what it is I dare not tell you now, Uncle
Jen," he added, gravely looking at the elder. "If you are wise, you
will not pursue your inquiry."
"Ah!" said Sarby, walking toward the door, "you will know the reason
when you learn the truth!"
After this enigmatical remark he hurriedly left the room, for the
purpose, without doubt, of escaping further questioning. His
demeanor completely puzzled Jen, who could not make out the
meaning of his conversation. Evidently David knew something which
he was unwilling to reveal--something which might lead to the
solution of the profound mystery which enwrapped the death of
Maurice and the extraordinary disappearance of his body.
The more Jen thought about the matter the more perplexed did he
become. The recovered devil-stick, found in the grounds of Mrs.
Dallas, the saturated handkerchief found in the bedroom of the dead
man; and now the unaccountable hints of David that he knew
something likely to throw a light upon these mysteries, joined with
an equally unaccountable refusal to afford such revelation, all these
things puzzled him; but as it was impossible in the absence of actual
knowledge, to come to any reasonable decision, Jen determined to
see Jaggard and see how he was. If Jaggard could only recover his
senses, argued the major, he would be able to say who had stolen
the body. Moreover, in Jen's opinion, the person who committed the
second crime would most probably, by the force of analogous
reasoning, have committed the first.
"Ever since that handkerchief has been removed sir," said she,
earnestly, "Jaggard has got well. I do believe, sir, that the scent on it
kept the poor dear stupid."
Another light was let in on Jen's mind. Here was the handkerchief
again--perfumed with the devil-stick decoction of poison by Dido,
applied by the hand of Etwald, and its design was evidently to keep
Jaggard in a state of stupor and prevent him from, making
dangerous disclosures. Dido and Etwald once more in partnership.
Jen was more convinced than ever that the pair were at the bottom
of the whole terrible affair.
"I am glad to see that you are better, Jaggard," he said, while
standing by the bed.
"Yes, sir, thank you, sir," replied the man, in a weak voice. "I'm sorry,
sir, but I couldn't help myself. I was drugged, sir."
"I guessed as much," said Jen, grimly. "And who drugged you?"
CHAPTER XVII.
Exhausted by the few words which he had spoken, Jaggard fell back
on his pillows in a dead faint. Seeing that further conversation was
impossible at the present moment, Jen left the patient to the tender
attention of Anne, and withdrew to seek David. He found him in a
melancholy mood, pacing up and down the lawn before the window
of the smoking-room. On perceiving his guardian, Sarby turned pale,
for he thought that Jen had come to continue their previous
conversation, and so force his confidence. But the first words of the
major at once undeceived him.
"Well, David!" said the newcomer, with significance, "I have made
one discovery without your help."
"I know who drugged Jaggard. I have learned who stole the body of
Maurice!"
"Then you know more than I do," replied David, with all the
appearance of truth. "My knowledge extends only to the death; not
to the seizure of the body."
"And you refuse to aid me," said the major, reproachfully; "well,
keep your secret, I may be able to do without your help. But," added
Jen, fixing a piercing glance on the young man, "I notice that you do
not ask me the name of the person who drugged Jaggard."
"Ah!"
Jen drew back a step and looked at his ward with marked surprise.
"No," he said, at length. "Mrs. Dallas has had nothing to do with it."
"That being the property of Mrs. Dallas, she had lost it there,"
interrupted Jen, smartly. "No. I told you also that Isabella had
confessed to having dropped it at the time of her midnight visit. But
now I know that she told me a lie!"
"Your mind seems to run on the mother, David," said Jen, looking
again at Sarby with keen inquisitiveness. "Can you prove by any
chance that she committed the crime?"
"Yes. You owe it to me--your second father--to tell the truth. You
owe it to your dead brother's memory--for assuredly Maurice was
your brother."
"I owe you much more than I can ever repay," said he, in harsh
tones. "All the same, Uncle Jen, I cannot reveal, even to you, what I
know. If I did so, you would be the first to blame me."
"And I answer for the last time that the truth is not mine to tell,"
replied David, coldly. "If you doubt me question Etwald."
"I can't give you my reasons. They would take too long to explain.
But I believe that out of jealousy he killed Maurice."
"Oh," said Sarby, ironically; "and out of jealousy he stole the body?"
"Dido?"
"Yes, Dido!" repeated Jen, firmly. "Jaggard has just informed me that
it was Dido who drugged him. Why did she drug him? To steal the
body of my poor lad. Why did she steal the body! To conceal the
crime committed by Etwald."
"Listen, then, and I shall explain," resumed the major, with growing
excitement. "I firmly believe that Etwald stole the devil-stick, and
with it killed Maurice."
"Well?"
"Well!" repeated Jen, in an irritated tone, "can you not rouse that
dull brain of yours to some understanding? To avert the discovery,
and to prevent the analysis of the poison in the body. Dido, under
the direction of Dr. Etwald, committed the third crime."
"Because the man has some power over her. What that power may
be, I know no more than you do. Although," added Jen, with an
afterthought, "you may be able to explain."
"If he only knew the truth," said he, wiping the perspiration from his
face, "what would he say? What would he do? He blames me now;
would he blame me then?"
The invalid remained silent for a time, then began to speak slowly
and with some little difficulty.
"After you left me, sir," he said in a weak voice, "I remained seated
in my chair beside the bedside of my poor young master. If you
remember there was only one candle in the room, which was placed
on the table, some little distance away. I examined the window and
found it closed."
"Quite sure, sir. It was bolted and barred. The door was simply
closed, for I never thought of locking it, as I fancied, sir, that you
might return after midnight to see if all was right."
"I did not, however, Jaggard. I fell asleep in the library, after Mr.
Sarby had gone to bed; and, of course, I had every confidence in
you."
"Please don't say that, major," said Jaggard, imploringly, "as I did my
best. It was not my fault that Dido drugged me. I'm sure I don't
know why she did so," continued Jaggard, half to himself. "I never
did her any harm."
"Do you not know what occurred during the time you were
insensible?" he asked, gravely.
"Well," said Jen, seeing that the man spoke in all good faith, "the
body of Mr. Maurice was stolen on that night."
"I can't tell, nor can anybody else. All we know is that at three
o'clock in the morning we entered Mr. Maurice's room and found the
window open, the body gone, and you insensible."
"I'm certain of it, major; and it was that black witch who stole the
body."
"Yes, major. It was this way. I was seated by the bed, at the foot of
it, with my face to the door. The window, as I said, was locked. She
could not have got in at the window, and had she entered by the
door I should have seen her. Besides," added Jaggard, in a faint
voice, "she grabbed me from behind."
"From behind?"
"Yes, sir. I was not quite asleep, but a kind of dozing in my chair. I
don't know what it was made me sleepy, as I was wideawake when
you left, sir. But there was a kind of heavy, sleepy smell about."
"Well, sir, the smell made me sleepy; and though I heard a noise
behind me I could not turn my head. I was just as if in a nightmare,
sir. Then the black arm of that witch came from behind me and
grabbed at my throat, and she held a handkerchief with that stuff on
it to my nose."
"Ah," said Jen, to himself, "I knew that Isabella was speaking falsely.
Go on, Jaggard," he added aloud. "Why did you not call out?"
"I couldn't, sir. I felt as in a dream; but I turned and tried to fight
her. She pushed me over, and I fell like a log. I think I must have hit
my head on a corner of the bed, for I felt a cruel pain at the back of
it."
"You did wound your head, Jaggard; and after that fall you
remembered no more?"
"No, sir, not till to-day. I don't know what it all means, sir, but I'm
sure I know how Dido got into the room."
"Ah! That is what I wish to learn. Well?"
"If you remember, sir. Dido called to see you that day."
"It was a blind, sir; and when she left the room I don't believe she
left the house."
"Sir, I took Dido out to the door, and while I was telling her to go
away. Dr. Etwald came out. He told me he would see after her, and I
left them alone. Now, sir," said Jaggard, with emphasis, "I do believe
as Dr. Etwald took that black jade to the room of Mr. Maurice and hid
her under the bed."
CHAPTER XVIII.
Angered by the selfish way in which David had acted, Jen did not
communicate his discoveries to the young man. During the night he
took counsel with himself, and the next morning he acted upon the
plans which he had formed. These were, to see Dido and force the
truth from her, to send Battersea to Deanminster to fetch both Arkel
and Dr. Etwald to "Ashantee," and finally to communicate his
discoveries to the inspector and get him to arrest Etwald. Once in
prison, and the doctor, intimidated by a fear of death at the hands of
justice, might confess his crimes, and his reasons for committing
them. This straightforward course was the only one to pursue.
After breakfast, therefore, the major wrote two notes. One for Arkel,
asking him to be at "Ashantee" by noon, as the writer had important
matters to discuss; the other for Etwald, requesting him to call and
see Jaggard, who, added Jen, significantly in the letter, had
recovered his senses. Having thus prepared his trap for the doctor to
walk into, Jen delivered the letters to Battersea, with instructions to
set off at once for Deanminster. The tramp, anxious to keep in favor
with Jen for cupboard reasons, lost no time in departing, and when
the major had seen him safely out of the gates, he took his way
toward "The Wigwam" for the all-important interview with Dido.
Before his departure he had left a message for David, who had not
made his appearance at breakfast, requesting the young man to be
in the library at noon.
"If I can force the truth out of Dido," thought Jen, strolling slowly
along in the hot sunshine, "I may get the better of Etwald. Then,
when David sees that the doctor is in the trap, and in danger of
arrest for murder, he may relate what he knows. Though upon my
word," considered the major, frowning, "I don't see what information
he can possibly add to what I have obtained from Jaggard, or what I
am likely to wring from the unwilling lips of Dido. Etwald is the guilty
person. David can tell me no more than that."
"Not yet. Dido," he said, in a cold voice. "It is true that I called to
see your mistress; but I wish to speak to you also."
Dido started, and cast an inquiring look at the impassive face of the
white man.
"Indeed, you did not. Dido. You did not inform me that by Dr.
Etwald's directions you filled the devil-stick with poison, or that you
steeped the handkerchief found in the room of Mr. Alymer in the
same poison for the purpose of drugging my servant; or again, that
you concealed yourself under the bed, and afterward drugged him."
A kind of terror showed itself in the dilated eyes of the negress. She
could not understand how Jen had become possessed of a
knowledge of her crimes, and at first was struck with stupor by the
recital.
"Nor," said he, fixing his eyes on the woman, "did you confess that
you opened the window of Mr. Alymer's room, and aided Dr. Etwald
to carry away the dead body?"
"Yes, the dead body of Mr. Alymer, which you and Dr. Etwald took to
his house at Deanminster. No denial, woman," said Jen, raising his
voice, as she was about to speak. "I see by your face that you are
guilty."
Dido trembled all over, whether from rage or fear Jen could not
determine, and opened her mouth to give the lie to her accuser.
Then she shut it again, as a heavy step was heard outside the door.
A moment later and Mrs. Dallas, with a face expressive of
astonishment, was standing on the threshold of the room; and Dido
at her feet was making the room resound like a jungle with howlings
like those of a wild beast. All the savage nature of the woman was
now on the surface, and had broken through the sullen restraint of
her impassive demeanor. "What is the meaning of this?" demanded
Mrs. Dallas, with an uneasy glance at the frantic negress.
"I shall explain when Dido stops her howling," said Jen, quite
undisturbed.
"Oh, missy! missy!" wept the negress, getting onto her feet. "It all
am a lie, what dat massa say. Poo' ole Dido know nuffin'--do nuffin'.
Lordy! Lordy! de big lie."
Major Jen took Dido by the shoulder, and giving her a good shake,
commanded her to be silent. At once the negress--who was
evidently acting a part--ceased her outcries, and after casting her
eyes significantly at her mistress, stared sullenly at the floor. Mrs.
Dallas turned pale at this rapid glance, and was obliged to take a
seat to prevent herself from falling. Not a detail of this by-play was
lost upon Jen, who saw in the conduct of mistress and servant a
confirmation of his suspicions. However, he added nothing to his
previous speech, but merely recapitulated--for the benefit of Mrs.
Dallas--the points of his accusation against the negress. Dido heard
him in silence, but this time she made neither outcry nor denial.
"It is a fact," insisted Jen. "I have the evidence of Jaggard to prove
that Dido was in the room on that night."
"No," said Dido, bluntly, "I say dat I in de room, but I no kill dat
man."
"Woman," cried Jen, with energy, "no one but you could
manufacture the poison with which the devil-stick was filled."
Dido hesitated, looked at Mrs. Dallas, and came out with a lie.
"Do you mean to say that Dido killed Mr. Alymer?" she asked,
nervously.
"No; but she supplied the means to the man who did."
"Impossible."
"By no means; and Dido manufactured the poison which was used."
"I know to what you allude," she said, after a pause. "Dido does
manufacture the drug, but only for the cure of nervous headaches."
"Or to kill men with," rejoined Jen, ironically; "or to drug the
watchers of the dead."
"Yis," said the negress, coldly; "de great massa told me to do dat."
"He took away the body of Mr. Alymer, and you helped him?"
"Yis."
"Where did you take it to?" demanded Jen, baffled in one direction
and trying another.
"On three charges. First, that he thieved the devil-stick; second, that
he killed Maurice; and third, that he stole the lad's body."
Mrs. Dallas fell back on the sofa, with a white face. Dido laughed in
a guttural fashion, and shrugged her shoulders contemptuously.
The major guessed that she meant that African witchcraft would
avert disaster from Etwald, and at once flung the word back in her
face.
"Voodoo will not help the doctor," said he, quietly. "This is a civilized
country, and we who inhabit it are above being influenced by such
degrading superstitions. You believe in Voodoo; in Obi; let us see if
such things will protect you."
"Do you mean that Dido is in danger of arrest?" cried Mrs. Dallas, in
a terrified tone.
"She filled the devil-stick with the poison which was used to kill
him," retorted the major, coldly, "and she confesses to having aided
him in stealing the body."
Mrs. Dallas was about to speak, when the negress silenced her with
a look, and raised her head proudly.
"Yis. It ole Dido," she said. "But ole Dido not lost. Dat great massa,
he look after ole Dido."
"If you mean Dr. Etwald, he will have enough to do to look after
himself. Well, Mrs. Dallas, as I have learned what I wished to know,
I shall now take my leave."
"No," said Jen, in an inflexible voice. "I go to punish the man who
killed my boy."
Without another word he left the room. His last glance showed that
Dido had gathered her sobbing mistress in her arms, and was
staring after him in a defiant manner. At the front door Jen heard his
name called softly, and Isabella, with a rich color in her usually pale
cheeks, came flying after him.
"Major, major, I have heard all! I have been listening at the window."
"Dr. Etwald?"
"No, not Dr. Etwald, but the person who stole the devil-stick."
"Ah! you know who committed the first of the crimes," cried Jen,
seizing the young girl's arm. "Confess. It was Dr. Etwald who stole
the wand of sleep."
"Dido?"
CHAPTER XIX.
FURTHER EVIDENCE.
"Yes; but she did not know what she was doing!"
Jen frowned.
"That is impossible!" he said, positively. "Quite impossible!"
"No! no! Wait! Listen!" said Isabella, much agitated. "I told you
falsehoods before to shield my mother. Now that I know that you
have discovered so much, that you are bent on punishing Dr. Etwald,
I must tell you the truth, so that she may not be dragged down to
ruin. But not here--not here: my mother may see us--and Dido," the
girl shuddered. "Dido, of whom I am afraid. Come with me, major.
Quickly!"
"Major," she said, when somewhat out of breath he had taken his
seat beside her in the summer-house, "although I relate what
inculpates my mother, it is to save her that I do so. Both she and I
are in a net woven by Dido."
"He was right to do so. Oh, you do not know what a terrible woman
she is. For years both I and my mother have been under her
influence; and have submitted to her will. Now, I see her in her true
colors, and I am determined to speak the truth. Save myself and my
mother, major; for we are innocent. Dr. Etwald and Dido are the
guilty persons."
Our website is not just a platform for buying books, but a bridge
connecting readers to the timeless values of culture and wisdom. With
an elegant, user-friendly interface and an intelligent search system,
we are committed to providing a quick and convenient shopping
experience. Additionally, our special promotions and home delivery
services ensure that you save time and fully enjoy the joy of reading.
ebookultra.com