On 08/08/06 13:45, Jarek Zgoda wrote:
> Steven Armstrong wrote:
> 
>> Don't know if this is related to your problem, but if you're using
>> sqlite the patch at [1] may help.
>>
>> If this does solve your problem, and you have a moment, you could add
>> some more background info about the bug to that ticket and confirm that
>> the patch worked. I was in a rush when I created it and haven't yet
>> taken time to add some more info for the devs.
> 
> This patch didn't solve my problem, I see no difference in behaviour.
> 
> The object with date field value of 2006-08-07 definitely exists (it is
> listed in month view), but trying to make a view of objects at URL
> 2006/08/07/ results in empty list, thus 404 if allow_empty == False. My
> urlconf contains entry for
> ^(?P<year>\d{4})/(?P<month>\d{2})/(?P<day>\d{2})/$, so above given URL
> should add items 'year': '2006', 'month': '08', 'day': '07' to generic
> view call arguments list. Month format is already '%m', day format is
> default. It seems that SQLite3 database contains character value of
> '2006-08-07' in this field.

This is exactly the problem that the patch fixes.
In MySQL and friends a DateField is represented as '2006-08-07 00:00:00' 
while in sqlite it's just '2006-08-07'.

The patch changes the archive_day view to test if it's dealing with a 
DateField or a DateTimeField and builds the sql lookup args depending on 
that.

Have you nuked any *.pyc files still lying around after applying the patch?

I had the exact same symptoms that you're describing and the patch 
solved the problem.

hope this helps
cheers
Steven

> 
> Will try with MySQL, although it's a bit of overkill to me.
> 
> Cheers
> Jarek Zgoda
> 
> 
> > 


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---

Reply via email to