@matigo :o as you were…
Think I might stay off spirits for the next few nights (maybe starting from tomorrow) to give my palate a bit of a rest before the Decanter tasting on Saturday.
Right, one last column to add: "eventtypeoverride" to winenotes, in case I ever buy 2 bottles (eventtype=1) but decide to take notes having brought one bottle to a restaurant (event_type 3). And if more advanced analysis were ever required, it would be a simple matter to say that if eventtypeoverride=null, event_type=1.
Because if I ordered the wine in the restaurant (i.e. not BYOB), the wines table would have a record for it with event_type=3, with no need for an override.
This makes my head hurt just a touch. Good thing I had my afternoon coffee.
@kdfrawg Indeed. I only started thinking about the inventory side a week or so ago, and it's not even immediately important — just a way of future-proofing and keeping as much data as I can…
Ah, of course. The simplest way would be to have a "Source" table, and then an "event type" table where "event type" is either "at home" or "tasting event".
@hazardwarning 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