Re: Test failures under Oracle

How about creating django.contrib.db.backends for databases with a small maintainer "bus size" number? Oracle and django-mssql could live there. They would have less than full support, but still some level of official recognition? -- Vernon Cole On Wednesday, May 1, 2013 4:31:58 AM UTC-6,

Re: Test failures under Oracle

Hi, now that the 1.6 release plan is out, I'd like to push this topic again. If you are using Oracle, now is the time to fix those bugs. Personally I am toying with the idea of dropping Oracle support from core if we can't ensure it's quality. Regards, Florian -- You received this message

Re: Test failures under Oracle

10.3.2013 23:03, Petite Abeille kirjoitti: On Mar 10, 2013, at 9:36 PM, Ian Kelly wrote: These particular lookups have a long history of being tweaked due to users coming up with installations where the existing queries did not work. See tickets #5985, #11017 and

Re: Test failures under Oracle

On Sun, Mar 10, 2013 at 3:03 PM, Petite Abeille wrote: > Another point perhaps worthwhile mentioning: > > # There's no way for the DatabaseOperations class to know the > # currently active Oracle version, so we do some setups here. > >

Re: Test failures under Oracle

On Sunday 10 March 2013, Florian Apolloner wrote: > and provide help there… Eg: https://code.djangoproject.com/ticket/20014 is > a perfect example where someone with Oracle knowledge can chime in, Here's a starting point, a query for the constraints affecting a table, from the South backend for

Re: Test failures under Oracle

On Mar 10, 2013, at 9:36 PM, Ian Kelly wrote: > These particular lookups have a long history of being tweaked due to > users coming up with installations where the existing queries did not > work. See tickets #5985, #11017 and #14149. I'd rather not reopen > this issue

Re: Test failures under Oracle

On Sun, Mar 10, 2013 at 2:15 PM, Petite Abeille wrote: > > On Mar 10, 2013, at 8:28 PM, Aymeric Augustin > wrote: > >> https://github.com/django/django/blob/master/django/db/backends/oracle/base.py#L548-L555 > > Last but not least… I

Re: Test failures under Oracle

On Mar 10, 2013, at 9:28 PM, Ian Kelly wrote: > Digging into the code a bit further, I see that the postgresql backend > accomplishes this by tacking '::text' onto the end of the field name > when the lookup is a string-based lookup like startswith. Oracle > could

Re: Test failures under Oracle

On Sun, Mar 10, 2013 at 1:44 PM, Petite Abeille wrote: > > On Mar 10, 2013, at 8:28 PM, Aymeric Augustin > wrote: > >> Django does this already: >>

Re: Test failures under Oracle

On Mar 10, 2013, at 9:12 PM, Florian Apolloner wrote: > Interesting. Out of curiosity may I ask what brought you to this ML then? Ah, oh, yes, well… subscribed to the django mailing lists a while back to see what was all the fuss about :) That specific thread caught

Re: Test failures under Oracle

On Mar 10, 2013, at 8:28 PM, Aymeric Augustin wrote: > https://github.com/django/django/blob/master/django/db/backends/oracle/base.py#L548-L555 Last but not least… I couldn't help notice these suspicious looking operators:

Re: Test failures under Oracle

Hi, On Sunday, March 10, 2013 9:00:57 PM UTC+1, Petite Abeille wrote: > > > Patches welcome… > Yes, I wish I knew Python. Sadly I don't. :) > Interesting. Out of curiosity may I ask what brought you to this ML then? (Don't get me wrong, it's just not that often that people write to this

Re: Test failures under Oracle

On Mar 10, 2013, at 8:45 PM, Florian Apolloner wrote: > Patches welcome… Yes, I wish I knew Python. Sadly I don't. :) > Well the issue is that nobody wrote get_key_columns yet, so we'd need a > patch which adds this method to the oracle backend, examples can be taken

Re: Test failures under Oracle

Hi, On Sunday, March 10, 2013 7:48:02 PM UTC+1, Petite Abeille wrote: > > (1) Whereabout way to get table metadata (i.e. query the table to figure > out its data to figure out its meta data). Instead, using the data > dictionary directly would be more reliable and to the point, e.g. select >

Re: Test failures under Oracle

On Mar 10, 2013, at 8:28 PM, Aymeric Augustin wrote: > Django does this already: > https://github.com/django/django/blob/master/django/db/backends/oracle/base.py#L548-L555 Perfect. In the case of #20015, the issue is the other way round… the literal

Re: Test failures under Oracle

On 10 mars 2013, at 20:08, Petite Abeille wrote: > > On Mar 10, 2013, at 7:56 PM, Petite Abeille wrote: > >> If you are not explicit, the session NLS format is applied, with >> unpredictable results. > > For the record, one can always set

Re: Test failures under Oracle

On Mar 10, 2013, at 7:56 PM, Petite Abeille wrote: > If you are not explicit, the session NLS format is applied, with > unpredictable results. For the record, one can always set this explicitly at the session level as well, e.g.: alter session set nls_date_format =

Re: Test failures under Oracle

On Mar 10, 2013, at 7:11 PM, Ian Kelly wrote: > #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

Re: Test failures under Oracle

On Mar 10, 2013, at 7:04 PM, Florian Apolloner wrote: > It's not always just SQL and even then, before formulating them in SQL it's > easier to just ask the Oracle users to take a look at the failing issues > and provide help there… Eg:

Re: Test failures under Oracle

On Sun, Mar 10, 2013 at 1:52 AM, Aymeric Augustin 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

Re: Test failures under Oracle

Hi, On Sunday, March 10, 2013 6:33:08 PM UTC+1, Petite Abeille wrote: > > > I'm only dealing with Oracle to fix failures in Django's test suite or > ensure that new features are supported under Oracle. Clearly I'm not smart > or knowledgeable enough to take advantage of its docs. > If you can

Re: Test failures under Oracle

On Mar 10, 2013, at 12:58 PM, Aymeric Augustin wrote: > On 10 mars 2013, at 10:34, Petite Abeille wrote: > >> On Mar 10, 2013, at 9:52 AM, Aymeric Augustin >> wrote: >> >>> Oracle's online

Re: Test failures under Oracle

On 10 mars 2013, at 10:34, Petite Abeille wrote: > On Mar 10, 2013, at 9:52 AM, Aymeric Augustin > wrote: > >> Oracle's online docs are a sad joke > > Specifically? The Oracle document is rather extensive and detailed. What's >

Re: Test failures under Oracle

On Mar 10, 2013, at 9:52 AM, Aymeric Augustin wrote: > Oracle's online docs are a sad joke Specifically? The Oracle document is rather extensive and detailed. What's confusing you? -- You received this message because you are subscribed to the Google

Test failures under Oracle

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