It has the potential to become very complicated with wines if you take that approach: you can have one table for each winery, but some wineries have land in 10 or 20 appellations. And while you could have a table of all appellations on the planet, it would be insanely long (because you have appellations within appellations).

I think, for the time being, I'll keep the winery and appellation fields within the "wine" table. It doesn't matter whether I change it now or in 10 years — if ever — because I'm at the point where I'd have no choice but to automate it.
// @kdfrawg

@kdfrawg Would you also advise having a "winery" table? Feasible, if I can automate generating that.

@kdfrawg Hmm, excellent idea.

Quite a difficult problem:
Given tables "wine" and "winenotes", where should the "source" (i.e. what shop, what event) field go?
If I put it in wine
notes, then "wines" is simply a table of wines in general, and serves as a sort of autofill.
If I put it in "wines", then if I ever buy 2 of the same wine from 2 shops, I have to enter it twice. Yet that might turn out to be an advantage, if I ever decide to add a "quantity" column (so, if I ever wanted to turn this db into a full cellar management system).

I suppose the latter solution would be more in line with the traditional concept of receiving a case of wine and working your way through it, then perhaps buying another case at a later time.

Bach and Dvorak in the same playlist? Interesting choice.

Maybe I should've had a more…hearty…dinner.

Because I'm quite hungry now. But it's too late to make popcorn — need to sleep.

Damn.

Surely even the Twitter team have private accounts and all the problems associated with them figured out by now.

Then again, there's probably very little motivation to have any trust in the people behind Twitter.

//

A simple dinner tonight, I think — ras el hanout carrot soup with pork sausage and potato cubes. 5 carrots just to make that tiny bowl of soup…huh.

Wealthy people are wealthy because they spend wisely? :P

Reeder's acceptable.
//