There are a couple of interesting features but just looking over the changes it looks like it resolves some caveats that Django has to supply workarounds for:
There's now a BOOLEAN datatype (from the tickets I've worked on this is by far the biggest pain point) quoting from the docs: "This enables you to store TRUE and FALSE values in tables and use BOOLEAN expressions in SQL statements."
SELECT now no longer requires a FROM
GROUP BY now supports column aliases & position numbers
I realise that we still support older versions of Oracle but perhaps at least there's some potential for fixing issues that couldn't be resolved due to the lack of bools if some version detection was put in place?
We still have to wait for a compatible driver, cx_Oracle and python-oracledb don't support it yet.
Best, Mariusz
charettes
unread,
Apr 17, 2023, 10:32:07 PM4/17/23
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Django developers (Contributions to Django itself)
Thanks for sharing the news David!
Support for true BOOLEAN type and GROUP BY position are effectively very welcome changes as they account for a few hacks. I do wonder if that's paving the way for grouping by subquery in future versions.
Best,
Simon
David Sanders
unread,
Apr 21, 2023, 3:54:45 AM4/21/23
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Django developers (Contributions to Django itself)