Re: Removing Oracle from Django core in 3.0

classic Classic list List threaded Threaded
18 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: Removing Oracle from Django core in 3.0

Tim Graham-2
I can't find a past discussion specific to Oracle, but it's not a new proposal. See https://groups.google.com/d/topic/django-developers/O-g06EM6XMM/discussion for "Moving database backends out of the core."

I think removing Oracle from core would only increase the maintenance burden. Since Oracle has edge cases, it's useful to test those along with new Django features. If the Oracle backend is in a separate repo, then adding new features will often require commits to two repositories and I don't know how we would run the tests with pull request X for Django and pull request Y for the Oracle backend. Then we also have to release the Oracle backend separately.

djangoci.com isn't reporting any Oracle failures on master. If you've found an issue, please open a ticket with details.

We don't run the Oracle tests with pull requests because they take about an hour, while other databases take about 10 minutes. It hasn't been difficult to identify which pull requests require running the tests on Oracle and to trigger that build with the trigger phrase.

On Sunday, November 25, 2018 at 5:21:02 AM UTC-5, Johannes Hoppe wrote:
Hi there,

I have recently refactored some bits in the database backend and came to realize that a lot of the complexity in there comes from the poor implementation of the Oracle backend.
Fun fact, did you know that Oracle tests don't run by default and that the current master, fails on oracle ;)

Anyhow, I want to come to a conclusion about the following matter:

Should we remove the Oracle database backend from Django core in the 3.0 release?

Here are a couple of reasons, why I believe this to be a good idea:
  • License
    • Oracle is  Proprietary software
  • Money
    • Oracle is not a sponsor of the Django Foundation, but makes 40bn in revenue
  • Technical:
    • Oracle does not support may features
    • due to its lack of features, a lot of edge case handling to the base database backend which drives overall complexity
  • Development:
    • Oracle does not run in the regular CI suite, in fact master is broken right now
    • entrance barrier for first time contributors is high
      • one needs to accept a non open source license
      • register with oracle
      • go through a very complex setup process
Of course there are some users who use Oracle and I don't want to keep them hanging. I simply believe the database backend should be developed separately from Django.
This could even be helpful for the Oracle community. Since oracle is enterprise only, they usually looks for longer support cycles than what Django want's to offer.

Ok, I made my case, I am curious, what do you guys think?

Best
-Joe

--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/d354b7a9-d116-41e9-9b4c-f8335931957f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Removing Oracle from Django core in 3.0

André Luis Pereira dos Santos
Move database backends out of the Django's core sounds great.
 

Em domingo, 25 de novembro de 2018 15:54:21 UTC-2, Tim Graham escreveu:
I can't find a past discussion specific to Oracle, but it's not a new proposal. See <a href="https://groups.google.com/d/topic/django-developers/O-g06EM6XMM/discussion" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/topic/django-developers/O-g06EM6XMM/discussion&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/topic/django-developers/O-g06EM6XMM/discussion&#39;;return true;">https://groups.google.com/d/topic/django-developers/O-g06EM6XMM/discussion for "Moving database backends out of the core."

I think removing Oracle from core would only increase the maintenance burden. Since Oracle has edge cases, it's useful to test those along with new Django features. If the Oracle backend is in a separate repo, then adding new features will often require commits to two repositories and I don't know how we would run the tests with pull request X for Django and pull request Y for the Oracle backend. Then we also have to release the Oracle backend separately.

<a href="http://djangoci.com" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fdjangoci.com\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHlhkus2nakMB0sCd5mtd7JSV7Z7A&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fdjangoci.com\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHlhkus2nakMB0sCd5mtd7JSV7Z7A&#39;;return true;">djangoci.com isn't reporting any Oracle failures on master. If you've found an issue, please open a ticket with details.

We don't run the Oracle tests with pull requests because they take about an hour, while other databases take about 10 minutes. It hasn't been difficult to identify which pull requests require running the tests on Oracle and to trigger that build with the trigger phrase.

On Sunday, November 25, 2018 at 5:21:02 AM UTC-5, Johannes Hoppe wrote:
Hi there,

I have recently refactored some bits in the database backend and came to realize that a lot of the complexity in there comes from the poor implementation of the Oracle backend.
Fun fact, did you know that Oracle tests don't run by default and that the current master, fails on oracle ;)

Anyhow, I want to come to a conclusion about the following matter:

Should we remove the Oracle database backend from Django core in the 3.0 release?

Here are a couple of reasons, why I believe this to be a good idea:
  • License
    • Oracle is  Proprietary software
  • Money
    • Oracle is not a sponsor of the Django Foundation, but makes 40bn in revenue
  • Technical:
    • Oracle does not support may features
    • due to its lack of features, a lot of edge case handling to the base database backend which drives overall complexity
  • Development:
    • Oracle does not run in the regular CI suite, in fact master is broken right now
    • entrance barrier for first time contributors is high
      • one needs to accept a non open source license
      • register with oracle
      • go through a very complex setup process
Of course there are some users who use Oracle and I don't want to keep them hanging. I simply believe the database backend should be developed separately from Django.
This could even be helpful for the Oracle community. Since oracle is enterprise only, they usually looks for longer support cycles than what Django want's to offer.

Ok, I made my case, I am curious, what do you guys think?

Best
-Joe

--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/1606db6d-af8b-4c74-866f-bc20b195b49c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Removing Oracle from Django core in 3.0

Adam Johnson-2
In reply to this post by Tim Graham-2
Interestingly, I didn't receive your first email Johannes, only Tim's reply. I can't even find it in spam. Maybe Gmail's filters highly associate mentions of "Oracle" with spam? :/

I agree that with Tim that it's going to be easier to keep it in core if development is going to continue. Any suggestion that unbundling it would improve its support lifecycle should be well backend by Django+Oracle users themselves, which I take it you aren't Johannes.

On Sun, 25 Nov 2018 at 17:54, Tim Graham <[hidden email]> wrote:
I can't find a past discussion specific to Oracle, but it's not a new proposal. See https://groups.google.com/d/topic/django-developers/O-g06EM6XMM/discussion for "Moving database backends out of the core."

I think removing Oracle from core would only increase the maintenance burden. Since Oracle has edge cases, it's useful to test those along with new Django features. If the Oracle backend is in a separate repo, then adding new features will often require commits to two repositories and I don't know how we would run the tests with pull request X for Django and pull request Y for the Oracle backend. Then we also have to release the Oracle backend separately.

djangoci.com isn't reporting any Oracle failures on master. If you've found an issue, please open a ticket with details.

We don't run the Oracle tests with pull requests because they take about an hour, while other databases take about 10 minutes. It hasn't been difficult to identify which pull requests require running the tests on Oracle and to trigger that build with the trigger phrase.

On Sunday, November 25, 2018 at 5:21:02 AM UTC-5, Johannes Hoppe wrote:
Hi there,

I have recently refactored some bits in the database backend and came to realize that a lot of the complexity in there comes from the poor implementation of the Oracle backend.
Fun fact, did you know that Oracle tests don't run by default and that the current master, fails on oracle ;)

Anyhow, I want to come to a conclusion about the following matter:

Should we remove the Oracle database backend from Django core in the 3.0 release?

Here are a couple of reasons, why I believe this to be a good idea:
  • License
    • Oracle is  Proprietary software
  • Money
    • Oracle is not a sponsor of the Django Foundation, but makes 40bn in revenue
  • Technical:
    • Oracle does not support may features
    • due to its lack of features, a lot of edge case handling to the base database backend which drives overall complexity
  • Development:
    • Oracle does not run in the regular CI suite, in fact master is broken right now
    • entrance barrier for first time contributors is high
      • one needs to accept a non open source license
      • register with oracle
      • go through a very complex setup process
Of course there are some users who use Oracle and I don't want to keep them hanging. I simply believe the database backend should be developed separately from Django.
This could even be helpful for the Oracle community. Since oracle is enterprise only, they usually looks for longer support cycles than what Django want's to offer.

Ok, I made my case, I am curious, what do you guys think?

Best
-Joe

--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/d354b7a9-d116-41e9-9b4c-f8335931957f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


--
Adam

--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMyDDM1LxFXXusWe-mJA55%2BqoK-9pr3-ZAK%2BV6Kw-igqNkaggg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Removing Oracle from Django core in 3.0

Dan Davis
My employer is an Oracle shop.  I would dedicate myself to Oracle specific bugs to prevent removing Oracle from core.   That said, we'll probably be off Oracle and onto the cloud and Postgresql by 3.0.

On Sun, Nov 25, 2018 at 1:36 PM Adam Johnson <[hidden email]> wrote:
Interestingly, I didn't receive your first email Johannes, only Tim's reply. I can't even find it in spam. Maybe Gmail's filters highly associate mentions of "Oracle" with spam? :/

I agree that with Tim that it's going to be easier to keep it in core if development is going to continue. Any suggestion that unbundling it would improve its support lifecycle should be well backend by Django+Oracle users themselves, which I take it you aren't Johannes.

On Sun, 25 Nov 2018 at 17:54, Tim Graham <[hidden email]> wrote:
I can't find a past discussion specific to Oracle, but it's not a new proposal. See https://groups.google.com/d/topic/django-developers/O-g06EM6XMM/discussion for "Moving database backends out of the core."

I think removing Oracle from core would only increase the maintenance burden. Since Oracle has edge cases, it's useful to test those along with new Django features. If the Oracle backend is in a separate repo, then adding new features will often require commits to two repositories and I don't know how we would run the tests with pull request X for Django and pull request Y for the Oracle backend. Then we also have to release the Oracle backend separately.

djangoci.com isn't reporting any Oracle failures on master. If you've found an issue, please open a ticket with details.

We don't run the Oracle tests with pull requests because they take about an hour, while other databases take about 10 minutes. It hasn't been difficult to identify which pull requests require running the tests on Oracle and to trigger that build with the trigger phrase.

On Sunday, November 25, 2018 at 5:21:02 AM UTC-5, Johannes Hoppe wrote:
Hi there,

I have recently refactored some bits in the database backend and came to realize that a lot of the complexity in there comes from the poor implementation of the Oracle backend.
Fun fact, did you know that Oracle tests don't run by default and that the current master, fails on oracle ;)

Anyhow, I want to come to a conclusion about the following matter:

Should we remove the Oracle database backend from Django core in the 3.0 release?

Here are a couple of reasons, why I believe this to be a good idea:
  • License
    • Oracle is  Proprietary software
  • Money
    • Oracle is not a sponsor of the Django Foundation, but makes 40bn in revenue
  • Technical:
    • Oracle does not support may features
    • due to its lack of features, a lot of edge case handling to the base database backend which drives overall complexity
  • Development:
    • Oracle does not run in the regular CI suite, in fact master is broken right now
    • entrance barrier for first time contributors is high
      • one needs to accept a non open source license
      • register with oracle
      • go through a very complex setup process
Of course there are some users who use Oracle and I don't want to keep them hanging. I simply believe the database backend should be developed separately from Django.
This could even be helpful for the Oracle community. Since oracle is enterprise only, they usually looks for longer support cycles than what Django want's to offer.

Ok, I made my case, I am curious, what do you guys think?

Best
-Joe

--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/d354b7a9-d116-41e9-9b4c-f8335931957f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


--
Adam

--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMyDDM1LxFXXusWe-mJA55%2BqoK-9pr3-ZAK%2BV6Kw-igqNkaggg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAFzonYZbZwqbBu1Pn9%3D0sGUUaZ_z05HqDs7gT3CgzUqeJ2d%3D5w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Removing Oracle from Django core in 3.0

Mariusz Felisiak
In reply to this post by Tim Graham-2
Hi

     I don't agree that the Oracle back-end is poor implemented (I probably should not treat this personally 😀). It is as well maintained as any other back-end that is in the core. We don't have much more open tickets in the Oracle back-end then in others and IMO it is easier to maintain it in the core.
  • Technical:
    • Oracle does not support may features
    • due to its lack of features, a lot of edge case handling to the base database backend which drives overall complexity
Just like SQLite or MySQL I don't think that we should leave only PostgreSQL in the core 😀.
  • Development:
    • Oracle does not run in the regular CI suite, in fact master is broken right now
I don't see any failures in djangoci.com. Maybe you use an unsupported version of Oracle?

Best
Mariusz


W dniu niedziela, 25 listopada 2018 11:21:02 UTC+1 użytkownik Johannes Hoppe napisał:
Hi there,

I have recently refactored some bits in the database backend and came to realize that a lot of the complexity in there comes from the poor implementation of the Oracle backend.
Fun fact, did you know that Oracle tests don't run by default and that the current master, fails on oracle ;)

Anyhow, I want to come to a conclusion about the following matter:

Should we remove the Oracle database backend from Django core in the 3.0 release?

Here are a couple of reasons, why I believe this to be a good idea:
  • License
    • Oracle is  Proprietary software
  • Money
    • Oracle is not a sponsor of the Django Foundation, but makes 40bn in revenue
  • Technical:
    • Oracle does not support may features
    • due to its lack of features, a lot of edge case handling to the base database backend which drives overall complexity
  • Development:
    • Oracle does not run in the regular CI suite, in fact master is broken right now
    • entrance barrier for first time contributors is high
      • one needs to accept a non open source license
      • register with oracle
      • go through a very complex setup process
Of course there are some users who use Oracle and I don't want to keep them hanging. I simply believe the database backend should be developed separately from Django.
This could even be helpful for the Oracle community. Since oracle is enterprise only, they usually looks for longer support cycles than what Django want's to offer.

Ok, I made my case, I am curious, what do you guys think?

Best
-Joe

--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/b5260d36-c698-4e3f-bf28-4d7c425d691e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Removing Oracle from Django core in 3.0

Johannes Hoppe


On Monday, November 26, 2018 at 8:27:02 AM UTC+1, Mariusz Felisiak wrote:
Hi

     I don't agree that the Oracle back-end is poor implemented (I probably should not treat this personally 😀). It is as well maintained as any other back-end that is in the core. We don't have much more open tickets in the Oracle back-end then in others and IMO it is easier to maintain it in the core.
Haha, sorry, I didn't mean to offend anyone. I hope you can see past my poor choice of works. I just noticed that a lot of oracle specific behavior is implemented in the base backend, where other backends like MySQL opt to override methods to add their db specific behavior. 
  • Technical:
    • Oracle does not support may features
    • due to its lack of features, a lot of edge case handling to the base database backend which drives overall complexity
Just like SQLite or MySQL I don't think that we should leave only PostgreSQL in the core 😀.
They are actually a lot better maintained then Oracle, which leads me to believe it's not used that often. Besides both DBs you mentioned are open source. I don't mind putting in extra work for an open source database. For a private corp that makes 4bn in revenue... not so much. Maybe a separate backend project, would also see more support from Oracle.
  • Development:
    • Oracle does not run in the regular CI suite, in fact master is broken right now
I don't see any failures in <a href="http://djangoci.com" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fdjangoci.com\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHlhkus2nakMB0sCd5mtd7JSV7Z7A&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fdjangoci.com\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHlhkus2nakMB0sCd5mtd7JSV7Z7A&#39;;return true;">djangoci.com. Maybe you use an unsupported version of Oracle?

Best
Mariusz


W dniu niedziela, 25 listopada 2018 11:21:02 UTC+1 użytkownik Johannes Hoppe napisał:
Hi there,

I have recently refactored some bits in the database backend and came to realize that a lot of the complexity in there comes from the poor implementation of the Oracle backend.
Fun fact, did you know that Oracle tests don't run by default and that the current master, fails on oracle ;)

Anyhow, I want to come to a conclusion about the following matter:

Should we remove the Oracle database backend from Django core in the 3.0 release?

Here are a couple of reasons, why I believe this to be a good idea:
  • License
    • Oracle is  Proprietary software
  • Money
    • Oracle is not a sponsor of the Django Foundation, but makes 40bn in revenue
  • Technical:
    • Oracle does not support may features
    • due to its lack of features, a lot of edge case handling to the base database backend which drives overall complexity
  • Development:
    • Oracle does not run in the regular CI suite, in fact master is broken right now
    • entrance barrier for first time contributors is high
      • one needs to accept a non open source license
      • register with oracle
      • go through a very complex setup process
Of course there are some users who use Oracle and I don't want to keep them hanging. I simply believe the database backend should be developed separately from Django.
This could even be helpful for the Oracle community. Since oracle is enterprise only, they usually looks for longer support cycles than what Django want's to offer.

Ok, I made my case, I am curious, what do you guys think?

Best
-Joe

--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/15a8d317-7749-43f4-a760-e07bb2aab74f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Removing Oracle from Django core in 3.0

Carlton Gibson-3
Hi Joe! 👋

On 26 Nov 2018, at 09:05, Johannes Hoppe <[hidden email]> wrote:

I don't mind putting in extra work for an open source database. For a private corp that makes 4bn in revenue... not so much. 

Is the issue “How to squeeze money out of Oracle?” — On that, did anyone try asking? 🙂
(I do feel that sentiment too.) 

C.

--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/D8BAF003-67FA-4C04-8944-C85D1FC81880%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Removing Oracle from Django core in 3.0

Florian Apolloner
In reply to this post by Mariusz Felisiak
Hi,

I personally agree with Mariusz here. Oracle might have it's own quirks, but the same could be said for any database. Taking my experience with the ORM into account I do not think that Oracle requires much more work (if at all) than any other database. I think in the end it does not matter whether one works around the limitations/features of Oracle or MySQL. All in all I think having Oracle is a good thing because databases like MSSQL and Informix/DB2 quite often behave similar to Oracle and just narrowing the core scope to MySQL/Pg/Sqlite might lead to a kind of tunnel vision.

Granted, Oracle might be a bit harder to install; but with the developer VMs and docker containers that argument doesn't really hold either imo.

Cheers,
Florian

--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/e15e8a55-f946-4633-90a6-d64fac714265%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Removing Oracle from Django core in 3.0

Johannes Hoppe

On Monday, November 26, 2018 at 9:49:46 AM UTC+1, Florian Apolloner wrote:
Hi,

I personally agree with Mariusz here. Oracle might have it's own quirks, but the same could be said for any database. Taking my experience with the ORM into account I do not think that Oracle requires much more work (if at all) than any other database. I think in the end it does not matter whether one works around the limitations/features of Oracle or MySQL. All in all I think having Oracle is a good thing because databases like MSSQL and Informix/DB2 quite often behave similar to Oracle and just narrowing the core scope to MySQL/Pg/Sqlite might lead to a kind of tunnel vision.

Granted, Oracle might be a bit harder to install; but with the developer VMs and docker containers that argument doesn't really hold either imo.
There is not official container and the one you can build from their repo, didn't work for me. Furthermore you need to register with oracle and give them your Phone number, just to download the python library bindings. So it is somewhat harder than others ;)

Cheers,
Florian

--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/be871f78-76b7-4c52-8172-748248347b82%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Removing Oracle from Django core in 3.0

Johannes Hoppe
In reply to this post by Carlton Gibson-3
Hahaha, yes kind of :P
If they become a corporate sponsor it shut up immediately ;)

On Monday, November 26, 2018 at 9:08:13 AM UTC+1, Carlton Gibson wrote:
Hi Joe! 👋

On 26 Nov 2018, at 09:05, Johannes Hoppe <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="Ae2rhgh3AgAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">in...@...> wrote:

I don't mind putting in extra work for an open source database. For a private corp that makes 4bn in revenue... not so much. 

Is the issue “How to squeeze money out of Oracle?” — On that, did anyone try asking? 🙂
(I do feel that sentiment too.) 

C.

--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/e745b5fe-ac1c-4cd7-bfc5-450d0e4920b3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Removing Oracle from Django core in 3.0

Jani Tiainen
In reply to this post by Johannes Hoppe


Johannes Hoppe <[hidden email]> kirjoitti ma 26. marrask. 2018 klo 11.05:

On Monday, November 26, 2018 at 9:49:46 AM UTC+1, Florian Apolloner wrote:
Hi,

I personally agree with Mariusz here. Oracle might have it's own quirks, but the same could be said for any database. Taking my experience with the ORM into account I do not think that Oracle requires much more work (if at all) than any other database. I think in the end it does not matter whether one works around the limitations/features of Oracle or MySQL. All in all I think having Oracle is a good thing because databases like MSSQL and Informix/DB2 quite often behave similar to Oracle and just narrowing the core scope to MySQL/Pg/Sqlite might lead to a kind of tunnel vision.

Granted, Oracle might be a bit harder to install; but with the developer VMs and docker containers that argument doesn't really hold either imo.
There is not official container and the one you can build from their repo, didn't work for me. Furthermore you need to register with oracle and give them your Phone number, just to download the python library bindings. So it is somewhat harder than others ;)

I've very successfully built docker images from Oracle official repo without any major problems.

Also since cx_Oracle 6 you can build db api bindings without oracle sdk libraries with simple pip install. Using those though requires client libs.

Not sure about registration process and is it needed for instant client or xe version.


Cheers,
Florian

--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/be871f78-76b7-4c52-8172-748248347b82%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAHn91ocaJHSSNKM2NB_PAEHude1vyb2apS0n3L9-E-vJecmvsQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Removing Oracle from Django core in 3.0

Simon Charette
In reply to this post by Johannes Hoppe
I haven't tried it out for Oracle yet but Tom Forbes' django-docker-box seems to make it a not-too-painful process[0]

Simon

[0] https://github.com/orf/django-docker-box#oracle

Le lundi 26 novembre 2018 04:05:41 UTC-5, Johannes Hoppe a écrit :

On Monday, November 26, 2018 at 9:49:46 AM UTC+1, Florian Apolloner wrote:
Hi,

I personally agree with Mariusz here. Oracle might have it's own quirks, but the same could be said for any database. Taking my experience with the ORM into account I do not think that Oracle requires much more work (if at all) than any other database. I think in the end it does not matter whether one works around the limitations/features of Oracle or MySQL. All in all I think having Oracle is a good thing because databases like MSSQL and Informix/DB2 quite often behave similar to Oracle and just narrowing the core scope to MySQL/Pg/Sqlite might lead to a kind of tunnel vision.

Granted, Oracle might be a bit harder to install; but with the developer VMs and docker containers that argument doesn't really hold either imo.
There is not official container and the one you can build from their repo, didn't work for me. Furthermore you need to register with oracle and give them your Phone number, just to download the python library bindings. So it is somewhat harder than others ;)

Cheers,
Florian

--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/ee9fa331-1606-48fb-9362-e86cd9f3c9ae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Removing Oracle from Django core in 3.0

Johannes Hoppe
To quote the documentation: https://github.com/orf/django-docker-box/blob/85780dcc81d62a4c0c1142b45eb69e825d97b074/README.md#oracle

"As usual Oracle is a bit more complex to set up. ;)


--
Johannes Hoppe

www.johanneshoppe.com

Want to chat? Let's get a coffee!
https://calendly.com/codingjoe/coffee

Lennéstr. 19
14469 Potsdam

USt-IdNr.: DE284754038
On 26. Nov 2018, 14:55 +0100, charettes <[hidden email]>, wrote:
I haven't tried it out for Oracle yet but Tom Forbes' django-docker-box seems to make it a not-too-painful process[0]

Simon

[0] https://github.com/orf/django-docker-box#oracle

Le lundi 26 novembre 2018 04:05:41 UTC-5, Johannes Hoppe a écrit :

On Monday, November 26, 2018 at 9:49:46 AM UTC+1, Florian Apolloner wrote:
Hi,

I personally agree with Mariusz here. Oracle might have it's own quirks, but the same could be said for any database. Taking my experience with the ORM into account I do not think that Oracle requires much more work (if at all) than any other database. I think in the end it does not matter whether one works around the limitations/features of Oracle or MySQL. All in all I think having Oracle is a good thing because databases like MSSQL and Informix/DB2 quite often behave similar to Oracle and just narrowing the core scope to MySQL/Pg/Sqlite might lead to a kind of tunnel vision.

Granted, Oracle might be a bit harder to install; but with the developer VMs and docker containers that argument doesn't really hold either imo.
There is not official container and the one you can build from their repo, didn't work for me. Furthermore you need to register with oracle and give them your Phone number, just to download the python library bindings. So it is somewhat harder than others ;)

Cheers,
Florian

--
You received this message because you are subscribed to a topic in the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/django-developers/dg8BUVHKOo4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/ee9fa331-1606-48fb-9362-e86cd9f3c9ae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/d638aa8b-c10a-4c3c-b6d4-a687d3d9d979%40Spark.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Removing Oracle from Django core in 3.0

Tom Forbes
Indeed, the initial setup of the database takes a horrendous amount of time (like 30 minutes to init an empty database!).

On Mon, 26 Nov 2018, 14:12 Johannes Hoppe <[hidden email] wrote:
To quote the documentation: https://github.com/orf/django-docker-box/blob/85780dcc81d62a4c0c1142b45eb69e825d97b074/README.md#oracle

"As usual Oracle is a bit more complex to set up. ;)


--
Johannes Hoppe

www.johanneshoppe.com

Want to chat? Let's get a coffee!
https://calendly.com/codingjoe/coffee

Lennéstr. 19
14469 Potsdam

USt-IdNr.: DE284754038
On 26. Nov 2018, 14:55 +0100, charettes <[hidden email]>, wrote:
I haven't tried it out for Oracle yet but Tom Forbes' django-docker-box seems to make it a not-too-painful process[0]

Simon


Le lundi 26 novembre 2018 04:05:41 UTC-5, Johannes Hoppe a écrit :

On Monday, November 26, 2018 at 9:49:46 AM UTC+1, Florian Apolloner wrote:
Hi,

I personally agree with Mariusz here. Oracle might have it's own quirks, but the same could be said for any database. Taking my experience with the ORM into account I do not think that Oracle requires much more work (if at all) than any other database. I think in the end it does not matter whether one works around the limitations/features of Oracle or MySQL. All in all I think having Oracle is a good thing because databases like MSSQL and Informix/DB2 quite often behave similar to Oracle and just narrowing the core scope to MySQL/Pg/Sqlite might lead to a kind of tunnel vision.

Granted, Oracle might be a bit harder to install; but with the developer VMs and docker containers that argument doesn't really hold either imo.
There is not official container and the one you can build from their repo, didn't work for me. Furthermore you need to register with oracle and give them your Phone number, just to download the python library bindings. So it is somewhat harder than others ;)

Cheers,
Florian

--
You received this message because you are subscribed to a topic in the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/django-developers/dg8BUVHKOo4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/ee9fa331-1606-48fb-9362-e86cd9f3c9ae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/d638aa8b-c10a-4c3c-b6d4-a687d3d9d979%40Spark.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAFNZOJNC_WNqOuymisOD_6tWNSSxu3yoKoJCt0KiugFX77Tm7Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Removing Oracle from Django core in 3.0

Dan Davis
Related question - how would I search for Oracle specific issues.   I found this query:


However, I'm not sure how much I can rely on the keywords.

--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/affc60fa-b182-4767-aae8-086f5ba8fe4a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Removing Oracle from Django core in 3.0

Tim Graham-2
That's the query I would use. The 'oracle' keyword might not be assigned completely but you can scan through all the "Database layers" tickets fairly easily and add it to any that are missing.

On Monday, November 26, 2018 at 12:25:06 PM UTC-5, Dan Davis wrote:
Related question - how would I search for Oracle specific issues.   I found this query:

<a href="https://code.djangoproject.com/query?status=assigned&amp;status=new&amp;keywords=~oracle&amp;component=Database+layer+(models%2C+ORM)&amp;col=id&amp;col=summary&amp;col=status&amp;col=component&amp;col=owner&amp;col=type&amp;col=version&amp;desc=1&amp;order=id" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fcode.djangoproject.com%2Fquery%3Fstatus%3Dassigned%26status%3Dnew%26keywords%3D~oracle%26component%3DDatabase%2Blayer%2B(models%252C%2BORM)%26col%3Did%26col%3Dsummary%26col%3Dstatus%26col%3Dcomponent%26col%3Downer%26col%3Dtype%26col%3Dversion%26desc%3D1%26order%3Did\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH27bOn19P6ZjmkQOUzduzTgXTtbQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fcode.djangoproject.com%2Fquery%3Fstatus%3Dassigned%26status%3Dnew%26keywords%3D~oracle%26component%3DDatabase%2Blayer%2B(models%252C%2BORM)%26col%3Did%26col%3Dsummary%26col%3Dstatus%26col%3Dcomponent%26col%3Downer%26col%3Dtype%26col%3Dversion%26desc%3D1%26order%3Did\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH27bOn19P6ZjmkQOUzduzTgXTtbQ&#39;;return true;">https://code.djangoproject.com/query?status=assigned&status=new&keywords=~oracle&component=Database+layer+(models%2C+ORM)&col=id&col=summary&col=status&col=component&col=owner&col=type&col=version&desc=1&order=id

However, I'm not sure how much I can rely on the keywords.

--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/0baf8e65-562b-428a-ac70-3db0e92c8dac%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Removing Oracle from Django core in 3.0

Dan Davis

Another related question - https://docs.djangoproject.com/en/dev/internals/contributing/writing-code/unit-tests/#testing-other-python-versions-and-database-backends provides some terse advice for running the unit tests with different backends.   Is that essentially what is happening with a test like https://djangoci.com/job/django-oracle-1.11/, or is it more specific?

On Monday, November 26, 2018 at 2:41:32 PM UTC-5, Tim Graham wrote:
That's the query I would use. The 'oracle' keyword might not be assigned completely but you can scan through all the "Database layers" tickets fairly easily and add it to any that are missing.

--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/5bfa1fe2-38b2-4086-bc57-f9badec93489%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Removing Oracle from Django core in 3.0

gg wwk
Firstly, greetings everyone I'm new here but I am looking to learn and use Django more so...

I see the edge cases being a issue but I am for Oracle going out of core.  And in order to maintain and/or expand MySQL support  how is the the implementation of MariaDB going so far?


Thanks,
gwk

On Mon, Nov 26, 2018 at 10:32 PM Dan Davis <[hidden email]> wrote:

Another related question - https://docs.djangoproject.com/en/dev/internals/contributing/writing-code/unit-tests/#testing-other-python-versions-and-database-backends provides some terse advice for running the unit tests with different backends.   Is that essentially what is happening with a test like https://djangoci.com/job/django-oracle-1.11/, or is it more specific?

On Monday, November 26, 2018 at 2:41:32 PM UTC-5, Tim Graham wrote:
That's the query I would use. The 'oracle' keyword might not be assigned completely but you can scan through all the "Database layers" tickets fairly easily and add it to any that are missing.

--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/5bfa1fe2-38b2-4086-bc57-f9badec93489%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAKQ93yuqg5UydMA083Bf-xvOt6OEMKe0nQW1EKPKdk%2Bb6RG%3DEg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.