The precession of a database
should be as accurate
as a writer, describing sweet
Eleanor, a naughty child
maintaining that she's cleaning
the kitchen, while stealing
all the fairy cakes.
The relationship between
all entity's, should give rise.
to the elimination of redundant data,
while the Structured Query Language,
should not be used to show us
Eleanor, who has her tongue out.
The capture of all data
should be clear and concise,
and the user interface
should be as well presented
as Eleanor is in a party dress.
But then it is noted,
that the party dress
is now smudged with icing,
something a database,
should not do is mismatch
rows in a table, where Eleanor
should be sat, carefully behaving.
The goal of the database
is to present informational
reports, unlike Eleanor's
reports that I quote,
"Day dreams in class a lot"
What a database should not do
is run rampant, on a sugar high
while lamenting that there are no
muffins, to be had and the
design was 6 pages long,
now with tiny pink pigs,
all drawn and carefully commented.
Written while I was relearning some basic SQL and in the need of a break consisting of several beers, my writing and my thinking got very muddled up. But I have always found this to be on one hand pleasing and on the other hand bizarre as experimental poetry goes.
The relationship between the order of designing a database and the disorder of a bored child is as much a contrast as anything in life and the interwoven madness very much a symptom of everyday living.