| 3 | What I need is the clarification about the following comment in Changeset 16520 |
| 4 | "Also, regarding the DatabaseCreation.set_autocommit() method: |
| 5 | |
| 6 | Stop using it for such tasks |
| 7 | Stop providing an implementation that tries to cover all the possible idioms a third party database backend DB-API 2 driver could need to activate autocommit. It is now left for third party backends to implement. " |
| 8 | Does this mean the psycopg2 2.4.2 introduced the bug or it is django bug? |
| 9 | |
| 10 | So the point is: Will the Changeset 16520 be part of the next django release or it is just a quick fix and for the next release it is up to psycopg2 developers to fix the problem definitely? |