I have no idea why I did that sorry.
I would say let people choose the timeEnd, if you read my e-mail about
first establishing a user-base, you'll understand why.  I think we should
just leave it as an un-required field.

On Wed, Jan 23, 2013 at 9:21 PM, hpsin <notifications@github.com> wrote:

> In dbClasses.py:
>
> > @@ -115,8 +115,9 @@ class Event(db.Model):
> >  	name 		= db.StringProperty(indexed=False, required=True)
> >  	location 	= db.StringProperty(indexed=False, required=True)
> >  	description	= db.StringProperty(multiline=True)
> > -	dateStart 	= db.DateTimeProperty(required=True)
> > -	dateEnd 	= db.DateTimeProperty()
> > +	date 		= db.DateTimeProperty(required=True)
> > +	timeStart 	= db.TimeProperty(required=True)
> > +	timeEnd		= db.TimeProperty(indexed=False)
>
> Why aren't we indexing the end time? Are we judging things based on now-3
> hours < start time? What good does the end time do from a functional stand
> point (i.e., we'll have events displayed that are over according to time
> ends).
>
> Would it be worth looking at auto-filling timeEnd with timeStart +3 hours,
> and then sorting by now < timeEnd?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/hpsin/fwf/pull/2/files#r2752927>.
>
>



-- 

*Ross Nanopoulos*

*B.S. Candidate in Computer Science*

*Case Western Reserve University*

*rdn21@case.edu*

*rnanopoulos@gmail.com*