Interesting but I'm concerned that it doesn't address the very common scheduling / time period overlap style queries.
Example 1: Multiple Date Columns in a Row. Matching with some filter period.
An Order Record has fields: OrderPlacedDate, ManufStartDate, ManufCompleteDate, OrderShippedDate, OrderRecievedDate, OrderPaidDate. (etc)
Query 1: At July 1, Show Value & Count of Active orders that had not started Manuf, Were being Manufactured, Were waiting for transport, Were in Transit, Were expecting payment, Were 90 days over due.
Query 2: List the orders that were in Manufacture sometime in the period Mon 4th - Fri 8th May 2015
Example 2. Comparing overlapping periods between 2 entities.
Two Tables in a Hospital.
PatientAdmissions: AdmissionDate, DischargeDate. Condition( Cancer | Burns | etc)
DoctorRoster: ShiftStart, ShiftEndDateTime, Specialty(Cancer | Burns |etc)
Query 1: Show List of Burns Patients & Burns Specialists in Hospital at noon 25 Apr 2015.
Query 2: Show Count of Burns Patients & Count of Burns Specialists, Grouped by Shift over the past 90 days.
The objective is to discover if we have sufficient clinicians to provide adequate care to a patient type.
Am I missing something?