While Prolog is primarily a programming language, it is also a database
according my definition which includes anything that can store and
recall things. If you have a narrower/refined definition which excludes
Prolog, that is fine.

It is possible, the OP is in a similar situation. If he is, he may want
to employ EAV-type design to handle attributes that are unknown at
design-time, while keeping in mind the reduced performance, SQL &
constraint support and increased code/complexity.

I also do not know his exact requires. But if his requirements are to
store things with widely varied attributes and/or attributes that will
not be known at design time, then I might suggest:

tMedia (mID, name)
tAttrib (aID, name)
tValue (vID, valAsTxt, valType)
tEAV (mID, aID, vID)

For a similar example see www.dbfordummies.com/example/ex111.asp

Let us verify your assertion. Please replicate the dbd example with a
non-EAV RMDB solution.

Neo wrote:
The OP knows some basics of what he plans to store. It apparently will
be a library for a media collection. So there are some initial entities
that he knows will exist (books, tapes, CDROM, DVD, jump drives,
journals, comic books, trading cards,...). So there is no reason for
him to put ALL data into the EAV table. So similar to pseudokeys, he
should avoid EAV as much as possible.

I won't replicate your mindless EAV, but I'll put out some examples.

here's one that deals with online media (email, Instant Messages,
blogs)
https://dspace.mit.edu/bitstream/172...1/56016821.pdf
he even reviews different DB models, including Object DB, and concludes
Relational is the way to go.

A link for digital library for music is here:
http://www.dml.indiana.edu/pdf/minib...n-jcdl2002.pdf
.. It provides a nice ERD for the OP to start building his system. It
should not be too hard to expand the model for other things like
movies/videos. Once you begin to store binary data, one type is the
same as another.

I'm sure the OP could find similar references, though it seems to take
a little tuning in GOOGLE (there are a lot of links that come back).

The point is: there is no reason for him to put everythingin an EAV.
Such a design will merely lead eventually to wailing and knashing of
teeth.
Ed