I think we already have this no?
See https://docs.djangoproject.com/en/4.1/ref/databases/#s-third-party-notes
for a list of 3rd party DB backends.
On Tue, 13 Dec 2022 at 10:31, Vasanth Mohan wrote:
> I second Jörg about better maintainability with tighter integrations.
>
> However, for the fun
I second Jörg about better maintainability with tighter integrations.
However, for the fun of stirring the pot, what's the opinion on letting
Django define an API for the ORM and letting a library deal with the
DB-specific implementation that generates the SQL for query? Django could
have a li
I tend to believe the opposite is true. Django was/is a successor in its
field, because it offers an "out-of-the-box" or "batteries included"
experience. Subsequently parts were shaped as needed for that bigger
picture, e.g. the ORM became what it is today.
Does anyone still remember django ve
Hi,
Given the small number of Django ORM maintainers, making the ORM standalone
will, among other things, increase the adoption of Django and bring in new
maintainers.
An ORM inspired by Django ORM with over 3000+ stars:
https://github.com/tortoise/tortoise-orm
--
You received this messag
