Hi Scott,
Thank you for your response, this is very helpful.
On Tuesday, January 26, 2021 at 11:38:18 PM UTC+1 foug...@apps.disney.com
wrote:
> Snowflake does not support lastrowid. So, we grab the last ID inserted
> with a 'SELECT MAX(pk_name) FROM table_name'. This is obviously prone to
>
Simon, you give me too much credit, that is step beyond what I'd thought of
:) It looks good to me.
Why not a dict of dicts or perhaps a dict of namedtuples instead? I think a
list might be a bit annoying to map back to the requested fields.
Maybe I will try to put a proof of concept together...
Hi Simon,
On Wednesday, January 27, 2021 at 5:54:42 AM UTC+1 charettes wrote:
> I think that's the best option here if we want to elegantly add support
> for this feature while maintaining backward compability. Something along
> the lines of ...
>
That is certainly an interesting approach. It
OK... urgh. I don't think there's a perfect answer here.
As you say Tim, assuming the "support unless EOL before the Django
version's EOL" we end up dropping the Python version before the LTS, which
is going to be just as "premature" as we have now, but for the x.0.
If I've not counted wrong
I think I need to go through all proposed options a few more times to
understand their differences and implications.
But what about a more pragmatic approach: Django supports the currently
supported Python versions at any given time. Except for our LTS versions, which
would never drop support.
> Except for our LTS versions, which would never drop support.
Mhm, I'd support such an approach only if we have a clear idea for security
issues. Assume LTS supports Python 3.x to 3.z. Python 3.x goes EOL and has
a security issue that affects Django LTS -- what do we do? On one hand
there are
