being down, the platform othen fails over
to re-send via the backup SMTP server.
Steve Mapes
Steven Mapes T/A Jigsaw Tech
E: st...@jigsawtech.co.uk
(https://link.getmailspring.com/link/cf847694-1156-4ba3-bc92-5f42d434b...@getmailspring.com/0?redirect=mailto%3Asteve%40jigsawtech.co.uk
the same
credentials.
Steve Mapes
Steven Mapes T/A Jigsaw Tech
E: st...@jigsawtech.co.uk
(https://link.getmailspring.com/link/e32a2c46-7b3e-441e-ab1b-879d066cf...@getmailspring.com/0?redirect=mailto%3Asteve%40jigsawtech.co.uk=ZGphbmdvLWRldmVsb3BlcnNAZ29vZ2xlZ3JvdXBzLmNvbQ%3D%3D)
P: +44(0)7974220046
Ah yes that's true, totally forgot about request.body just then even though I
was using it a few days ago. So yes renaming it would help in that regard as I
do remember seeing a few S/O question where it's confused people in the past.
Mr Steven Mapes
Software Development and Solutions
E: st
Combined them would be very very bad and you would have the same problems
as with $_REQUEST in PHP where you have to decide which one wins as you can
make a POST to a URL with querystring where one of the parameters uses the
same name as a element of the POST and but where the value is
I also thought it was a taken more form HTTP rather than PHP but if this is
changed please do not use *request.form_data* as that is also misleading as
you can POST many more sources than form data such as with APIs. post_data
would be much clearer.
On Tuesday, 5 May 2020 22:26:34 UTC+1, Adam
This is the big thing for me which seems to be have been forgotten.
If you need to quickly upgrade a Django project from using url to re_path
the fastest way with the least amount of code changes is to simply alias
the import in your urls.py files I.E ```from django.urls import re_path as
I completely agree with James. I felt dread when I saw a JWT Thread appear
as, for me synonymous with flaws security and I'd rather Django stay well
clear of them
On Monday, 27 April 2020 03:53:39 UTC+1, James Bennett wrote:
>
> On Sun, Apr 26, 2020 at 8:46 AM Adam Johnson >
> wrote:
> >
> >
This is more an issue at the file system level and the hardware not being
able to keep up rather than anything Django is doing. It's the same
fundamental principal for why you may turn off webserver logging to
increase performance, writing to disk is expensive and so when dealing with
high
Perhaps I'm totally missing the point and use case for this but is there
any reason you are not simply using any of these
if expected_key is not in request.GET:
return MyErrorResponse(...)
if not request.GET.get("expected_key", None):
return MyErrorResponse(...)
required = ["one",
It sounds to me like your data modelling is wrong. You can either have a
one-to-one table2 acts as an extension of table1, a view that combines
multiple tables into one "virtual table" or have one table and two models
that use the table. One, the superset, would be managed, the other would
10 matches
Mail list logo
