#34200: Allow setting postgres role during connection setup
-------------------------------------+-------------------------------------
Reporter: Mike Crute | Owner: Mike
| Crute
Type: New feature | Status: new
Component: Database layer | Version: 4.1
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mike Crute):
Replying to [comment:7 Florian Apolloner]:
> I think this makes sense and is hard to achieve otherwise short of
overriding the backend. I am wondering if explicitly supporting role makes
sense though. Would a more generic approach like `init_command` in mysql
help? Then again we never had the need for this in postgresql so I rather
explicitly support `role` (or `assume_role` maybe) -- this way we can
easily shuffle it around in the backend code if needed.
I don't think this is a general concept, it's pretty specific to the
postgres security model. I'm happy to call it either `role` or
`assume_role` if you have a preference (I do not). Given that it's pretty
postgres specific that would mean it should stay in `OPTIONS` right?
--
Ticket URL: <https://code.djangoproject.com/ticket/34200#comment:11>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070184e6461fcc-56475160-4523-41e6-8986-98e251bad9f4-000000%40eu-central-1.amazonses.com.
