A very comprehensive answer. I am suitably impressed. There are two things I'd do differently.

You noted that your cultural stuff was simplistic. It makes the error of associating languages with countries. An artwork being produced by an artist who lives in the UK in no way means that the artwork is in English. It may be artwork in a foreign language. It may be artwork produced a long time ago. (Latin was once the official language here.) It may be artwork in a British minority language such as Irish Gaelic, Welsh, Scots, Scottish Gaelic, Cornish, or Cumbric. (Side note: prior to Brexit, the UK used to get funding from the EU for supporting Irish Gaelic as a minority language. It is also spoken as a minority language in the Republic of Ireland, but they are ineligible for getting similar funding because although it's spoken by a minority of Irish people, it is one of Ireland's two official languages, and you can't get funding for supporting your own official language. Other side note: Scots and Scottish Gaelic are two entirely different languages. Scots is a cousin of Modern English. Modern English and Scots both evolved from different dialects of Old English. Scottish Gaelic is more closely related to Irish Gaelic, Welsh, Cornish, and Cumbric. Scots and Scottish Gaelic are about as related as French and Greek.)

The other thing I'd do differently is to drop these three columns entirely:

create table painting (
    painting_id smallint unsigned not null primary key auto_increment,

create table poem (
    poem_id smallint unsigned not null primary key auto_increment,

create table play (
    play_id smallint unsigned not null primary key auto_increment,

[download]

All three of these tables already have a column which is not null and with each row having a unique numeric value.

toby döt ink

In reply to Re: DBIx::Class and "complex" joins (was Re^4: DB: what kind of relationship?) by tobyink
in thread DB: what kind of relationship? by bliako

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.