fundamental design issues with trips and dives

[Richard Houser]

Agreed.  It's just an arbitrary container.

Consider the less crazy case of going on a trip with a group near West Palm Florida for example.  They aren't die hard divers, but have 6 dives spread across a week.  It's still a dive trip.

Then you hear a college buddy is in-state on vacation, and arrange a couple extra dives in a cave up-state.  This is all happening while everyone else is out doing land based activities.  That's also a dive trip, and the two overlap.

I could even see the case with the above example of a dive being in two different trips if two groups overlapped at the same dive site, but that's pushing an edge case....

On November 7, 2019 12:40:04 PM EST, Linus Torvalds <torvalds at linux-foundation.org> wrote:
>On Thu, Nov 7, 2019 at 9:17 AM Dirk Hohndel <dirk at hohndel.org> wrote:
>>
>> (4) ??? other ideas?
>
>Stop thinking that dates have anything to do with dive trips.
>
>A dive is in a trip. A trip is just a container. The date is
>completely and utterly irrelevant, and has nothing to do with what
>trip a dive is.
>
>The *only* thing the date is used for trip-wise is the initial
>heuristic of which trip to put a dive in (or whether to create a new
>trip). Nothing else.
>
>Anything that believes that trips are anything but collections of
>random dives is fundamentally broken.
>
>          Linus
>_______________________________________________
>subsurface mailing list
>subsurface at subsurface-divelog.org
>http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.subsurface-divelog.org/pipermail/subsurface/attachments/20191107/bc88a636/attachment-0001.html>