On Feb 25, 2011, at 11:23 AM, greenpoise wrote: > > exactly, no overlapping date ranges
If I were doing it, I think I'd start with a (renamed) copy of gluon.validators.IS_NOT_IN_DB in my model file, and change it to do a range check on two fields, instead of an equality check on one. I'm sort of fuzzy on how you do date comparisons, but presumably there's a way. > > > > > > On Feb 25, 11:14 am, Jonathan Lundell <[email protected]> wrote: >> On Feb 25, 2011, at 11:01 AM, greenpoise wrote: >> >> >> >>> How could I combine these two? I have a table that accepts two dates. >>> I would not like duplicates between in those entry dates. >> >>> Basically a From Date and a To Date >> >> So the restriction is essentially: no overlapping date ranges in the >> database? >> >> >> >> >> >>> Thanks >> >>> Dan
