Is it possible to consider adding support for Oracle Database?

[smhegde-1979]

Currently, django-cte hard codes "WITH RECURSIVE" based on postgres recommendations. This is just a straight up syntax error. This unfortunately restricts use to postgres (and other DBs that support RECURSIVE).

Is it possible / feasible to consider adding support for Oracle back-end?

Also, we already have a custom Manager for our models, so are there any examples of using CTEManager in addition to our manager?
I think inheriting from django_cte classes has some issues. For e.g. in "With.queryset", an object of CTEQuery is directly instantiated so any subclass I have created from CTEQuery gets ignored.

[millerdev]

@smhegde-1979 would it work on Oracle if the RECURSIVE keyword were added on recursive queries only, or are other changes required in addition to that?

Also, we already have a custom Manager for our models, so are there any examples of using CTEManager in addition to our manager?

Have you looked at the Custom QuerySets and Managers documentation? Is it possible to make your custom manager extend CTEManager?

in "With.queryset", an object of CTEQuery is directly instantiated so any subclass I have created from CTEQuery gets ignored.

Can you provide a code example that demonstrates the issue and report it as a new issue, please?

[smhegde-1979]

Regarding your first question - If the RECURSIVE keyword is removed, I believe it works for my straightforward use cases.
Regarding the custom-managers, yes I looked into that and that is what I am doing. Good to know that is the way.

For the RECURSIVE keyword realted changes itself, would you need a code example? Really, its any of your examples but the back-end needs to be oracle to reproduce this issue.