Thank you both a lot! I knew it was simple, not sure why I couldn't figure
it out.
Thanks!
On Sat, Sep 13, 2008 at 12:55 PM, Keith Eberle <[EMAIL PROTECTED]>wrote:
> Building on Marcelo's response, and an example from James Bennett's book
> (Ch 5), you could also add a custom manager. It'd go s
Building on Marcelo's response, and an example from James Bennett's book (Ch
5), you could also add a custom manager. It'd go something like this:
class PublishedEntryManager(models.Manager):
def get_query_set(self):
return super(PublishedEntryManager,
self).get_query_set().filter(pub_date_
2008/9/12 Dana <[EMAIL PROTECTED]>:
>
> Hey all,
>
> Wondering what the best technique would be to make sure that an entry
> (such as a blog entry/story/etc...) with a datetime object 'pub_date'
> does not show up on the front end if the pub_date is in the future. I
> would assume using ".filter(.
Hey all,
Wondering what the best technique would be to make sure that an entry
(such as a blog entry/story/etc...) with a datetime object 'pub_date'
does not show up on the front end if the pub_date is in the future. I
would assume using ".filter(...something...)" is the way to go but
what would
4 matches
Mail list logo
