#35036: sqlsequencereset needs set search_path
-------------------------------------+-------------------------------------
Reporter: Ramon | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Normal | Resolution: duplicate
Keywords: sqlsequencereset | Triage Stage:
postgresql15 search_path schema | 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:
Replying to [comment:2 Ramon]:
> Database was created on PostgreSQL 15 and has a private schema, which
works fine when running the application.
> It is only the sqlsequencereset command output piped to dbshell that
fails.
It works because you set `-c search_path=your_db_schema`, nonetheless
Django doesn't do anything specific to support it. If you made the effort
to set `search_path` in your `DATABASES` configuration, you can add the
same to the generated script. `sqlsequencereset` is only of things that
may or may not work with `search_path`, that's why it was marked as a
duplicate of #6148.
--
Ticket URL: <https://code.djangoproject.com/ticket/35036#comment:3>
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/0107018c69e93d87-2e357aa0-40de-49a0-9c2b-fdae9c58fb69-000000%40eu-central-1.amazonses.com.
