#5223: Bug on sqlite __year comparison
---------------------------------------------------+------------------------
   Reporter:  Manuel Saelices <[EMAIL PROTECTED]>  |                Owner:  
nobody          
     Status:  new                                  |            Component:  
Database wrapper
    Version:  SVN                                  |           Resolution:      
            
   Keywords:  sqlite orm sq-rf sprintsept14        |                Stage:  
Accepted        
  Has_patch:  1                                    |           Needs_docs:  0   
            
Needs_tests:  1                                    |   Needs_better_patch:  0   
            
---------------------------------------------------+------------------------
Comment (by msaelices):

 Sorry, I havent logged before posting my comment
 
 Replying to [comment:13 anonymous]:
 > Replying to [comment:12 mtredinnick]:
 > > Firstly, there should be ''no'' tests failing. Otherwise you might be
 having other problems.
 >
 > Ok. I consider it's a Django problem, because many failed tests refers
 (I think) to have differents locales that people that usually runs all
 tests (things like {{{Expected: July, Got: Julio}}}. Other fails test
 refer to new file session backend, and I've considered as usual in a
 sprint like this, with many changes in a little time.
 >
 > It's another question, but I attached this
 [attachment:tests_report_07_09_16.log tests report] on this ticket.
 >
 > >
 > > Secondly, do any extra tests (particularly the "basic" one -- just run
 that on its own as Fredrik indicated) fail when you ''do not'' have the
 patch in place?
 >
 > Here I know that you said to locate patch lines in another situation
 {{{Field.get_db_prep_lookup}}}. But, I thought previous comments of
 failing tests was made with my patch and possibly location doesn't matter.
 Sorry If I was wrong.
 >
 > >
 > > The problem we are trying to work through is that without this patch,
 we can't get the existing tests to fail on the SQLite version Fredrik and
 I have tried, so it isn't clear that this is fixing a real problem. It may
 turn out to be tied to some particular bug in 3.3.5, in which case that's
 going to be hard cheese for users of 3.3.5. Or it might be something else,
 but right now, we don't have a clear demonstration of something that fails
 before the patch is applied and then starts working afterwards.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/5223#comment:14>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django updates" 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-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to