Using an intermediate object "Play" (abstraction of a track being played during an episode), a UML diagram <https://www.planttext.com/?text=JO-n2W8n38RtFaNefC8DhZSTWhk3Bn3RWENQNcdgKCHtD-sTXna2-RylX4nSC9TNy8fd5nDc3C2bUfAUdUdawIm1XLGg10eFogoCHsQu9iUBiBS2A1dDp8UZ-cpmteAEaiVQ202j2__QJU1kaOqasGYNPV64KQpV3NtMWpxfrHz1WvHMVMhnq8JjvaudYhOzy0K0> might look like:
[image: image.png] On Mon, 10 Jun 2019 at 23:02, sergio ruiz <sergio....@gmail.com> wrote: > these numbers are super tiny.. > > 25 episodes so far with about 15 tracks per episode.. > > > > On Jun 10, 2019, at 1:36 PM, James Foster <smallt...@jgfoster.net> wrote: > > The disadvantage is extra time doing the lookup. But before you discount > this approach, ask yourself what performance penalty this will cost. How > many episodes? How many tracks? Do you have less than 10K of each? How many > milliseconds does it take to do a “brute-force” search? I strongly > recommend: > > > ---- > peace, > sergio > photographer, journalist, visionary > > Public Key: http://bit.ly/29z9fG0 > #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV > http://www.codeandmusic.com > http://www.twitter.com/sergio_101 > http://www.facebook.com/sergio101 > >
