Code

Opened 7 years ago

Closed 7 years ago

#4692 closed (fixed)

Document required database user permissions

Reported by: Carl Karsten <carl@…> Owned by: nobody
Component: Documentation Version: master
Severity: Keywords: sql sprintsept14
Cc: Triage Stage: Ready for checkin
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description (last modified by mtredinnick)

On the db setup page http://www.djangoproject.com/documentation/databases/

There should be some specs on what rights django needs.

easies way to define it is with the command:

grant all on djangosite.* to djangouser identified by 'abc' with grant option;

For the various dbs.

Only A) someone should figure out what rights are really needed,
and B) maybe come up with 2 users, one for creating tables with manage.py syncdb.

I can see the attitude of "if you are going to run a server you should know" but this doesn't do much good for people who just want to try it out, and i like the DBA attitude of 'you prove to me why you need it and I'll give it to you."

Attachments (1)

4692.diff (2.5 KB) - added by ubernostrum 7 years ago.
Patch explaining necessary privileges

Download all attachments as: .zip

Change History (6)

comment:1 Changed 7 years ago by mtredinnick

  • Description modified (diff)
  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Summary changed from sql rights to Document required database user permissions

comment:2 Changed 7 years ago by Simon G. <dev@…>

  • Triage Stage changed from Unreviewed to Accepted

#4757 was marked as a dupe.

Changed 7 years ago by ubernostrum

Patch explaining necessary privileges

comment:3 Changed 7 years ago by ubernostrum

  • Triage Stage changed from Accepted to Ready for checkin

Attached a patch to install.txt explaining minimum necessary privileges for setting up a database for Django's use, and to testing.txt reminding users that creating a test database requires CREATE DATABASE.

comment:4 Changed 7 years ago by ubernostrum

  • Has patch set
  • Keywords sprintsept14 added

comment:5 Changed 7 years ago by adrian

  • Resolution set to fixed
  • Status changed from new to closed

(In [6260]) Fixed #4692 -- Documented required database privileges. Thanks, ubernostrum

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.