#34083: Cloning test database fails with mariadb-server 8.x
-------------------------------------+-------------------------------------
Reporter: Stephen Finucane | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 4.1
(models, ORM) |
Severity: Normal | Resolution: duplicate
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => duplicate
Comment:
There is no reason to open a duplicate. Please add a comment to the
original ticket. Also, I don't think you've explained the issue in enough
detail to confirm a bug in Django. It looks like a misconfiguration.
Please reopen the ticket (#33537) if you can debug your issue and provide
details about why and where Django is at fault.
We can also consider your suggestion to check if `returncode` is non-zero.
Personally, I think it makes sense. Please suggest this in the original
ticket.
Duplicate of #33537.
--
Ticket URL: <https://code.djangoproject.com/ticket/34083#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070183c6d48b78-4f56d8af-c5a4-4a90-b2f7-19ecd725bdb3-000000%40eu-central-1.amazonses.com.
