I posted a thread a while back about the latest version of Oracle 23c which
appears to add support for a few things that would fix some of the
workarounds we have in the ORM (eg boolean expressions). I know dropping
19c is a long way off but at least the future is looking brighter 🌟
On Wed, 9 Aug
I've had to deal with adding Oracle support to the features I've worked on
recently and with Mariusz's pointer to the right bit of the wiki
(https://code.djangoproject.com/wiki/OracleTestSetup) I was able to get a
working local development setup. I think once you have this local dev setup,
work
Thanks for raising this Paolo. It's good to discuss, even if we maintain
the status quo.
I think this will come to a head when Mariusz steps away. It's been him
that's kept it going the last few years, and I'm not at all sure that we
have another currently active contributor that's an Oracle exper
Hi Mariusz,
On Thu, Aug 3, 2023 at 8:47 PM Mariusz Felisiak
wrote:
> I'm quite surprised that you've started a new thread for something that was
> already discussed, you could always add a comment to the existing thread e.g.
> https://groups.google.com/g/django-developers/c/dg8BUVHKOo4/m/5uFVmd
Hello,
when I got started with Django more than 10 years ago, I had inherited a legacy
project with an Oracle database for porting from PHP to Python. It might also
have worked out well if Oracle support had been a 3rd party package, but I can
say for sure that Oracle being a core feature of Dj
Hi Paolo,
I'm quite surprised that you've started a new thread for something that
was already discussed, you could always add a comment to the existing
thread e.g.
https://groups.google.com/g/django-developers/c/dg8BUVHKOo4/m/5uFVmdWCAwAJ
> I wanted to share the frustration of seeing yet a
I don't have a strong opinion in either direction here.
I would like to point out that every database we support is a maintenance
burden, however. It's an exaggeration that Oracle alone causes problems but
other backends don't. For example when I was working on collations, I ran
into issues with S
+1 from my side for removing oracle support from django itself.
If very low usage + high maintenance burden does not qualify for feature
removal, idk what does - maybe not being supportive at all. Oh wait...
In the end such low usage numbers are prolly better served by a 3rd
party package.
On Thu, Aug 3, 2023 at 6:26 PM Paolo Melchiorre
wrote:
> Hi all,
> I wanted to share the frustration of seeing yet another great new ORM
> feature blocked due to Oracle compatibility:
> https://github.com/django/django/pull/16417
>
> In the past, I too have had to put a lot of effort trying to ma
Hi all,
I wanted to share the frustration of seeing yet another great new ORM
feature blocked due to Oracle compatibility:
https://github.com/django/django/pull/16417
In the past, I too have had to put a lot of effort trying to make a PR
compatible with Oracle, making the overall contributing expe
10 matches
Mail list logo
