On Sun, Mar 10, 2013 at 1:52 AM, Aymeric Augustin <[email protected]> wrote: > Hi folks, > > At the moment, a few tests are failing under Oracle. I've created tickets for > each of them: > > https://code.djangoproject.com/ticket/20010 > https://code.djangoproject.com/ticket/20011 > https://code.djangoproject.com/ticket/20012 > https://code.djangoproject.com/ticket/20013 > https://code.djangoproject.com/ticket/20014 > https://code.djangoproject.com/ticket/20015 > > The core team is notoriously under-qualified when it comes to maintaining > support for Oracle — we don't have 6-figure budgets for consulting and > Oracle's online docs are a sad joke. > > If you'd like future versions of Django to continue supporting Oracle, please > have a look at these tickets and help us fix them!
#20015 looks like an expected failure. Oracle supports lookups of date fields using strings by implicitly converting the string to a date. The test is doing a startswith lookup that is going to produce sql that looks something like "WHERE date_column LIKE '2008%'". That's not going to work because Oracle can't convert '2008%' into a date. So the test here is testing that the 'supports_date_lookup_using_string' feature is more comprehensive than Oracle actually supports. I'll try to make time to look at the other tickets in more depth tomorrow. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
