Hi
I don't agree that the Oracle back-end is poor implemented (I probably
should not treat this personally ). It is as well maintained as any other
back-end that is in the core. We don't have much more open tickets in the
Oracle back-end then in others and IMO it is easier to maintain it
My employer is an Oracle shop. I would dedicate myself to Oracle specific
bugs to prevent removing Oracle from core. That said, we'll probably be
off Oracle and onto the cloud and Postgresql by 3.0.
On Sun, Nov 25, 2018 at 1:36 PM Adam Johnson wrote:
> Interestingly, I didn't receive your
I guess it would help to know how Safari's tracking protection does work (I
do not own a Mac) -- it seems hard to imagine that an internal redirect on
a page triggers the protection. In that sense it seems more like a
ISP-problem like Adam pointed out.
On Sunday, November 25, 2018 at 9:39:28
Interestingly, I didn't receive your first email Johannes, only Tim's
reply. I can't even find it in spam. Maybe Gmail's filters highly associate
mentions of "Oracle" with spam? :/
I agree that with Tim that it's going to be easier to keep it in core if
development is going to continue. Any
Move database backends out of the Django's core sounds great.
Em domingo, 25 de novembro de 2018 15:54:21 UTC-2, Tim Graham escreveu:
>
> I can't find a past discussion specific to Oracle, but it's not a new
> proposal. See
>
Vue.JS could be a candidate to create that. I am currently experimenting
in adding a plugin system to Django in form of an app "GDAPS" - Generic
Django App Plugin System, find it on PyPi/Gitlab. It's in a very, very
rude state at the beginning, and I am not an experienced developer.
But I'd like
I can't find a past discussion specific to Oracle, but it's not a new
proposal. See
https://groups.google.com/d/topic/django-developers/O-g06EM6XMM/discussion
for "Moving database backends out of the core."
I think removing Oracle from core would only increase the maintenance
burden. Since
I have run into this problem myself in the past. On a previous project we
added a helper function to make deepcopy's of named attributes during
setUp().
>From a check against a few projects and Django's test suite[2] I have only
> identified a single issue which is that attributes assigned during
It sounds to me that this your email provider rewriting the link to go
through their tracking site, and Safari now blocks the tracking site. I
don't see how Django can do anything around this - the "internal token
redirect" (which I guess means a Django generated redirect from one page to
another
That does seem like an unintentional bug, since the code is forming a
string under the condition "if file_hash is not None:".
On Sun, 25 Nov 2018 at 03:26, Richard Campen
wrote:
> Hello
>
> I am currently looking at implementing a custom file hashing function when
> using the ManifestFilesMixin
10 matches
Mail list logo
