On 1/26/07, Panos Laganakos <[EMAIL PROTECTED]> wrote: > Though, not sure what "in the future" means. a matter of the date not > being the same in the db and the server or something? Care to explain?
Well, let's take a simple example. Today is January 30; if you were to go hit a generic view, and the only content in your database had a pub_date of January 31, then by default it won't show anything -- January 31 is in the future, so that content hasn't been "published" yet. Setting allow_future=True changes that so it will show the "future" items. This way we can balance between the most common case -- people wanting date-based archives of past content -- while not making it impossible to handle other cases (like event calendars which need to show things that haven't happened yet). -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
