Thank you Tim for all the hard work you have put into this!In your opinion, do you think it will be ready/merged before the big freeze?On 16 Sep 2017 03:23, Tim Graham wrote:Hi,Tom got sick and hasn't been able to work on the documentation as he'd hoped. If anyone wants to help, I left some TODOs
Hello
I would like to add that the application level joins are scripted such that
they are *atomic in nature. *Which means if there is another thread/process
operating in parallel, It will have no impact on final output. Is this why
you feel an application join is scary?
Regards
Nes Dis
On Fr
Hi,
Tom got sick and hasn't been able to work on the documentation as he'd
hoped. If anyone wants to help, I left some TODOs (denoted by XXX) on the
pull request: https://github.com/django/django/pull/9072. I'll be offline
tomorrow morning (EDT) but I hope to resume work on it around 1700 UTC
You're right for pointing out that some elements of a relational database
can be emulated in a non relational one, like Mongodb. The in-python joins
sound s bit scary though.
However I would argue that if you find yourself needing such things your
data is relational, and therefore a relational dat
I would like to thank everyone for their valuable comments. Simultaneously
I would like to comment on some conceptions regarding using MongoDB. Its
not accurate to state that relational joins cannot happen in MongoDB. It
can be done at the application level. LEFT JOIN and INNER JOIN. A detailed
About the timing, it's too late to get this in to Django 2.0 as the feature
freeze is on Monday and I already have a large queue of review work to do
before then. I don't think it makes much difference since features
deprecated in both Django 2.0 and 2.1 will be removed in Django 3.0.
On Friday
(For some reason GMail is clipping your message before any content, I only
saw '... [Message clipped]' and had to click to see it all)
I'm not that familiar with the static file storages, but it seems to me
like it's not going to be that controversial deprecate it in order to save
this duplication
On Friday 15 September 2017 11:35:49 Shai Berger wrote:
> On Friday 15 September 2017 11:09:58 Anssi Kääriäinen wrote:
> >
> > def simple_execute_hook(execute):
> > # One-time configuration and initialization.
> >
> > def execute_hook(sql, params, many, context):
> > # Code to
I agree with everyone, no relation with relational should not be mixed
because they solve different problems.
On the other hand, having an Object Document Manager (instead of an ORM) if
required could be a possibility, right?
I think until a lot of people have that need, it won't happen.
I've u
On Friday 15 September 2017 11:09:58 Anssi Kääriäinen wrote:
> Would it make sense to use the same technique used for HTTP
> request/response middleware? That is, the hook would look a bit like this:
>
> def simple_execute_hook(execute):
> # One-time configuration and initialization.
> def
Would it make sense to use the same technique used for HTTP request/response
middleware? That is, the hook would look a bit like this:
def simple_execute_hook(execute):
# One-time configuration and initialization.
def execute_hook(sql, params, many, context):
# Code to be executed
11 matches
Mail list logo